We have been ‘playing’ with PowerShell 3.0 for use with our new Sextant product. It was introduced in the fall of 2012 and is a huge upgrade from earlier versions of PowerShell, VBscript, or the various other scripting environments which have come before. PowerShell now has over 2,600 cmdlets.In previous versions PowerShell would do 70% of what was needed for Windows automation. For Windows 8 and Server 2012, PowerShell is now the basis for new management dashboards and can automate every part of the operating system. PowerShell can also load new libraries of cmdlets from third party vendors.
We feel that too few FileMaker developers have fully explored the use of PowerShell within their solutions. Before we get into ‘why PowerShell?’, let’s look at the bigger picture. Many of us have been looking for ways to replace of client-side plug-in functionality as FileMaker Go does not support plug-ins, not to mention many developers struggle with the installation, support, and/or registration of client-side plug-ins.
PowerShell can be run on any Windows 7/8 system; however, in our minds the best scenario is to run PowerShell from the server. This method would support Mac, Windows, and/or iOS when using a Windows-based FileMaker Server. PowerShell can run a command and send the results to a file as CSV or XML- two formats that FileMaker can handle with ease.
If you have been playing with FileMaker and PowerShell, or have been considering it; we would love to hear from you…