Not enough information...
How are the file references to the external files defined?
Can you post the script that you run through PSoS? I want to see how you establish context there.
Keep in mind that a script that you run through PSoS will also run your onOpen scripts so if anything fails there you may not actually get to the script that you had in mind.
Here's a screenshot of the full script I'm running. You can see all of my server-side logging that I'm doing. The external file references are all definied in "External Data Sources" and are FileMaker files. Everything works perfectly on the client.
I'm navigating to the correct layout, entering find mode and looping through the list of IDs that I sent in. Really straightforward.
Here's a snipped of what gets printed during the RelationInfo step:
Orders:: = Receipts::<File Missing>
Hopefully this is helpful in getting to the bottom of this. Thanks!
can you post a screenshot of how your file reference are defined in "external data sources"?
Are all the files on the same server?
Do you have the same user/pass on all files that you have when you're logged in?
Yeah. Same credentials on the files, and all are authorized using the FMPro authoriziation. I'm actually using the admin [Full Access] privilege set.
what happens if you explicitly use the "open file" script step to open all the necessary files instead of relying on FM to pull them open?
That's an interesting idea. I tried it and it still didn't work though.
Are the files all in the same directory (folder)? At one point in the past, there were issues with performing scripts in files in different folders. Can't remember if it ever got fixed.
Sadly they're not. If that's the case then it's a bitter pill because some of these files are massive and I'm going from an older organization method to a new one. I'll try it out with this shell file, since it's small enough to not make a difference.
Just gave it a shot and it still didn't work.
Good catch by Mike. That issue also exists for regular server-side scheduled scripts.
Can you post a screenshot of the folder structure (in the OS) and how you tried to solve it in the file references? The file reference needs to use relative paths like "./filename" so it is very unintuitive on how to solve it.
I briefly tried something along this line myself and was not able to get it to work.
I have seen it claimed somewhere that "the separation model doesn't work for PSOS" and that this is a known bug or limitation.
It does seem like there is some kind of general problem with multi-file solutions and PSOS.
Perhaps it is solvable - but it looks like the solution isn't obvious and we will need to figure out and carefully document some details.
I've put together some test files and I can not replicate the issue. Here's my setup
FileA, hosted on FMS13 but physically located in FolderA on the server
FileB, hosted on FMS13 but physically located in FolderB on the server
File reference from FileA to FileB, using the relative syntax: File:FileB
Relationship in FileA to FileB
I have a script in FileA that:
creates a new record and uses a call to the RelationInfo function
creates a new record and grabs the first related value from fileB
Screenshots below. As you can see I am getting the result that we are expecting. It looks like the folder structure is a red herring in this case. Back to an account mismatch?