Baseelements plugin export container field windows#
The BE_SMTPAddAttachement was used in a script that runs on an a Windows Server 2016, running FileMaker server 17, using the latest BE plugin. 1) To illustrate that the ‘Export Records’ approach worked, when I opened the JSON file in a text editor (TextMate) and did a Save As, the default format indicated is set to UTF-8. Using a micro-service you can export any field, container or otherwise, to any directory anywhere. Audio recordings stored directly do work as expected. BESaveURLToFile BaseElements Plugin Help Centre https. I have tested this with images stored directly from the camera, and also images pulled from the devices photo library. However, manually exporting the field contents from in FileMaker and then dragging the file back into the container field also works. In the workaround script, I used BE_ExportFieldContents to export the container field, and then BE_FileImport to bring the image back into the container field.
Running the same script on a client (MacOS, FileMaker 16 or 17) the image is attached normally.Įxporting the image from the container field to a hard drive and then importing it back into the container field allows the BE_SMTPAddAttachment to work. This occurs only when BE_SMTPAddAttachment is run in a scheduled server script. When an IOS device (in my case, an iPad or iPhone) running FileMaker Go 17 saves an image directly from the camera into a container field or from the photo library, using BE_SMTPAddAttachment fails with error 22 when attempting to add the image as an attachment.
0 kommentar(er)
