The speed of an import is really determined more by the specs of the machine that is doing the work, however FileMaker server does have an advantage in that it doesn't have to run any user interface, so some operations can be quicker. Export the contents there to a csv file and attach it to a support request.
![baseelements filemaker plugin runtime baseelements filemaker plugin runtime](https://www.mbsplugins.de/images/searchfield.jpg)
![baseelements filemaker plugin runtime baseelements filemaker plugin runtime](https://www.productivecomputing.com/wp-content/uploads/edd/2018/02/Outlook-Manipulator-demo-email-details-in-filemaker.png)
You can find the details of the error by going to the BaseElements Data file, and to the "ServerLog" layout. If there are any issues while importing, the "Importing on Server" will be changed to " Error when Importing". While the DDR is importing, the Solution Name will be appended with " Importing on Server". While you're waiting, control returns to BaseElements and you can continue to use it as normal. Your import will then process the XML files as normal on the local client, and once that is complete, it will hand over to the FileMaker Server via Perform Script on Server so that the import steps will be run on the server.
#BASEELEMENTS FILEMAKER PLUGIN RUNTIME PRO#
If you're a FileMaker Pro client connected to a copy of BaseElements shared from FileMaker Server then there will an extra option when importing a DDR.Īfter selecting a summary file, there will be a radio button choice for "Local" or "Server" imports :Ĭheck the option for Server, and click Continue. There's no specific setting to enable server side imports.
#BASEELEMENTS FILEMAKER PLUGIN RUNTIME INSTALL#
Must have either installed the BaseElements plugin on the FileMaker Server already, or enabled the option to allow scripts to install plugins.Once the import is complete, it will return to the UI file, showing the details of your just imported solution. Leave it running, and any issues that happen will be shown via a dialog. Because the XSLT transform happens in the plugin, if you have a large DDR it can at times appear that FileMaker is locked up. Large DDRs ( could be anything from 500MB and up ) will take time to import. Click Continue when you're done.īaseElements will show you progress for the import. These are optional, only the name is useful here.
![baseelements filemaker plugin runtime baseelements filemaker plugin runtime](https://i.ytimg.com/vi/voC0CnbWZnI/hqdefault.jpg)
You can then select some options for the import, such as Name, Version and Client. This file will be called something else if you're using a different language version of FileMaker. On the top left side of the Home layout is the import button.Ĭlick this button, and then select the "Summary.xml" file you generated when you created the DDR. Open BaseElements and go to the Home screen. Once you've generated your Database Design Report, you then need to import it into BaseElements.