Powershell sometimes parses things in quotes strangely, which is solved by putting backticks (`) around the quotes like so: AI_ORGANIZATION=`"My Company, Inc`" the script now works as intended. FileMaker puts two slashes in front of disabled script steps so you can identify them. AI_ORGANIZATION="Company" works, but not AI_ORGANIZATION="Company, inc."įINAL EDIT: I wanted to post an update because I finally found the problem, which wasn't really with Filemaker at all, but with PowerShell. Click the Disable button in the Edit Script dialog box. Is there something I'm missing? EDIT After further testing, the problem only seems to happen if the AI_ORGANIZATION property has multiples words, i.e. But also a script, scriptparameter, variables and a home-url can be passed as. Like I said, if I remove AI_USERNAME and AI_ORGANIZATION from this command, it executes just fine, but the user has to specify username and organization, which defeats the purpose of a silent install. Directly login WebDirect file with user and password in FileMaker 16.
#DISABLE SCRIPT IN FILEMAKER PRO 16 HOW TO#
This is the command I'm using: msiexec /i "$($env:userprofile)/desktop/Filemaker Pro 16.msi" AI_USERNAME="$UserName" AI_ORGANIZATION="My Organization" AI_LICENSEKEY=XXXX-XXXX-XXXX-XXXX AI_USERNAME=1 AI_REGISTRATION=0 AI_SKIPDIALOG=1 How to open a FileMaker database that has a startup or onOpen script that is broken, stuck in an endless loop, crashes the database, or simply prevents the d. This dialog only appears if I specify those two properties, None of the other options I include in the command seem to cause this issue. Instead a help dialog box for msiexec comes up. Scripts can perform tasks ranging from simple things (such as simply entering Find mode) to complex automated import/export processes, multitable reporting, data reconciliation, and really anything that can be expressed as a programmed series of FileMaker steps. msi file fails if I include the AI_USERNAME and AI_ORGANIZATION properties in the command line. Scripts are written in FileMaker Pro's ScriptMaker, a point-and-click interface.
#DISABLE SCRIPT IN FILEMAKER PRO 16 INSTALL#
The problem I'm having: using msiexec to install from the. I've been using the network install guide here for reference: I'm working on a powershell script to silently install FM Pro 16 on my users work stations with minimal input. Hoping this is the right place to find help for this.