![]() Thank you so much for the confirmation of what I was seeing & Happy New Year. When I was initially setting it up, I think I started looking at expanding it in more ways, but on running into the issue that the script server is unable to run this function, I have made sure that I don't take it too deep and that it stays in that first level of user-triggered scripts (so that scripts that are possibly ever triggered on the server are not dependent). The Execute Script function eliminates the need for an extensive "if/else if" series of statements to explicitly mention each possibly targeted button script. It then uses ExecuteScript to call the intended script. When a portal button is clicked, it looks up the related "script name" listed on the targeted button's record. ![]() The users choose the applicable buttons which are listed in their own table and appear on various layouts using portals. ![]() I'm using execute script to allow more flexible layouts so that users can choose which buttons & Report options appear on their layouts. Sorry for the delay, there was a glitch in my email, and I just found your message today. Reply to this email directly or view it on GitHub #73. However, if I am mistaken and BE_ExecuteScript can/should work as part of a server scheduled script, please let me know and I'll resume testing in my system. The issue isn't critical, I've only just started using the function and can plan accordingly to not use it on scripts that will be scheduled on the server. Some other BE functions do work from a scheduled script (as a simple test, BE_TimeZoneOffset worked fine), so I think the plugin is installed correctly and overall works, just not this particular function. We're using filemaker server 12.0.5.551 and the base elements plugin 2.1.0.0. I've started using the BE_ExecuteScript in a number of places (very helpful!), but have noticed that it doesn't seem to run when part of a filemaker server scheduled script. What were you trying to do that requires the ExecuteScript function? We don’t specifically lock out server side functions, so it’s possible to do things that make no sense ( like dialogs ) on server, so you need to be careful about what you call. Link to comment Share on other sites More sharing options. Running other scripts via the plugin API on server is probably just not supported. The easiest way to get it right is to create a FM file that uses the 'install plugin file' script step, and call it from both a PSoS and WebDirect - that way FMS itself will put it in the right place with the right permissions. I think this will be a server side issue.
0 Comments
Leave a Reply. |