![]() ![]() Lots of minor fixes and changes, some new functions, and new additions to other functions. There are a lot, all the details, as always are in GitHub : v4.1.4 will run on centos and 4.2 and later will be ubuntu only. ![]() What happened to centos?įileMaker Server for linux was a centos version of linux, but is now ubuntu, and so we’re only building for a single platform. So this means you can have a Mac plugin in windows, without breaking the Mac folder/bundle format. gz file and it will come in as uncompressed. So you can insert a plugin into a container field using the insert file step, and select a. Gz is just another compression format, but it has the advantage of it being the internal compression format for FileMaker container fields. Please contact us if you notice anything. This isn’t a final 4.2 release, that will come shortly, but it passes all our tests and is just waiting on some time out in real testing to make sure there’s nothing we’ve missed. With FileMaker 19.3 out, and now with native support for the new Apple M1 processor, plus a new Ubuntu release for FileMaker Server, there’s a need for a new BE plugin. You can delete the container fields after the import if required, just access the data on the BaseElements data file layouts.It’s been a bit slow here on the releases, but things are hectic at Goya with lots of development going on all over the place. So your BaseElements files will take up a lot more space on disk when you utilise this option. The greatest advantage is more than you're not locking up your copy of FileMaker Pro while the import is happening and you can continue working as normal.īaseElements is storing a copy of the XML for all the files within container fields in tables in BaseElements. We've found FileMaker Server imports to be faster than a local FileMaker Pro import, but your experience may vary and it will depend a lot on hardware. 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. 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. 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.
0 Comments
Leave a Reply. |