Export Container doesn't work on FMServer

[dburnham]

I have Scriptmaster installed on Filemaker Server 16, and on my iMac workstation as well in FMPA 17.   The Export Container example works perfectly on my workstation when connected to the server, but when the same script is executed on the server, nothing is written to the destination file path  FileMaker Server/Data/Documents.

I know that the script is running properly on the server because all other elements of the script run.  It is intended to send an email message with an attachment that is exported from a container field.   The email is delivered, but missing the attachment and that's because the export to the "Docs" folder fails.

I also observe that there is a significant difference in GetFieldName when the container is set to use remote storage.  Instead of the name of the field in the container, you get a multi-line string that defines the remotely stored object.  As such, it's not the name of the container object the same way is it is when the container content is embedded.

[john renfrew]

which version of SM???

[dburnham]

5.1

[john renfrew]

There is an issue which I know that 360works are aware of and working to fix with this version to do with the fmpro.getContainerStream method....

It's tricky because some older versions, which do work, might not load properly on Server 17 - those might be fine on FMS16.. Don't think it will be too long before there's a fix.

[dburnham]

Can you venture a guess about how long "too long" might be?   I am patient but would like to know.

[jaylkjr]

Ouch, I have not used it yet, nor even tested it, but had been planning on using that Export Container function.  What is the update on this?

[Dennis Burnham]

Base Elements can solve this for you.

[john renfrew]

#patientlydrummingfingers

little frustrated - this has been ongoing since last August