what they meant was that you should use the "export field content" script step to export from the container to your desktop. Not to the server.
Under no circumstances should you attempt to access the externally stored container data files on the server directly (through file sharing). While they are stored outside of FM, they are still managed by FM and you should only access them through FM.
Hi Wim, thanks for your response. But if i make a script button on the container to export the content then this will not work when I'm using Go.. Should the script first look what operating system is used, maybe digferent layouts for Go and desktop, what is most clever? In my opinion this issue is a big flaw (as a referencelink it doesn't work , while for exporting the file must also be picked up first (through the referencepath) .. What is 'Go' actually doing differently when immediately opening from server?
Hopefully there is a workaround?
Generally/typically, you would always branch your code after detecting what platform you are on. Not all script steps and functionality are supported on all platforms.
Same with layouts: given how different the form factor is and how you interact with the UI, I would create dedicated layouts for the FM Go workflows.
Excuse for the late respons; thanks for clearing this up!