Josh Ormond

What is the calculation doing? If this calculation is triggering a large data grab from other tables or grabbing data from several relationship hops away, along with a lot of other necessary behaviors to make the calculation work, this can be the reason it's slow on the first action. After that, all that data would be cached, and appear much faster.

What are you trying to do? There are ways to avoid the CORS issues, but they often depend on using a different method. The suggestion will depend on what your are actually trying to do that you are running into CORS issues.

Overall it's fine. You have to be mindful of the differences between 18 and 19 for the end users... But it is safe to use Pro 19 with Server 18. We have most of our users on 19, Server is 18.0.4. We are waiting for new hardware for our move to FMS 19.

Version 18 was the last version that had the Runtime in it. Support ended for version 18 in June 2021. https://support.claris.com/s/answerview?anum=000034564&language=en_US

You can change the color of the checkmark in the style section of the inspector, and also conditional formatting. The size is controlled, typically, by the font size. So likely something with the CSS went pear-shaped. I'm also in the camp of using a button bar for "checkboxes". https://blog.beezwax.net/fun-with-button-bars-check-please/

This is almost always not true. Typically the problems like you are seeing are file specific. And even often layout specific ( not saying yours is ). This is a diagnostic step that helps point to where the problem could be. If it does show in a brand new file, that points to a completely different problem than if it shows only in one file. As another diagnostic step, copy that object to a new layout with the default theme. Paste in the object, and set the style to the default in that new layout and whatever theme it uses ( if 19, likely Apex Blue ). With the new style applied, does it still show? If yes, DEFINITELY create a new file and see if the problem exhibits there also.

JSONGetElement ( $json ; "data.hijri.date" ) Replace $json with where you have the json string stored.

There are a couple of DDR analysis tools that can help find stuff. I use FMPerception and BaseElements. Mostly FMPerception. With that you could search through the DDR to see if there are references to IP addresses, etc. Hopefully all of your stuff is being handled via internal DNS. Then you just need to repoint the DNS to the new IP address. You could also swap the IP address to the new server. All depends on what your IT policies are. Some "Insert From URL" script steps, "Open URL", and plugin functions specifically might have references to other stuff. A big thing is, don't guess, open a copy of the files on the new server and test it to within half an inch of its life. See what is broken.

A lot depends on how the External Data Sources are set up. In the attached screenshot, the one we use almost exclusively, is: file:directoryName/fileName This allows FileMaker Server to look within the same directory as the current file for another file that is connected as an External Data Source. So often our File Path is something like ( where the actual file name is 'data.fmp12' ) file:data If this is the case for you, most file references should still work when moved to the new server, as long as the folder structure inside the FileMaker Server/Data/Databases/ path is the same ( assuming the server is using the default FileMaker Server database path ). If, however, the references are something else, there may be more work involved.

The FileMaker Developer Subscription is a set of tools, access to prerelease software, and a test-only version of FileMaker Server ( can't be used for a production server ). It's $99USD/year. It's not buying a "new FDS" with every version. If the DMT alone doesn't have $99 worth of ROI, then you likely don't need the DMT. Just speaking from reading the conversation, and a cursory evaluation of the info you provided. That is obviously an evaluation only you can make for sure. Is the value higher than the cost? I think the version 17 DMT might work... but it's a dangerous maneuver. I wouldn't even attempt it. You may not see the problems it causes for a while, and by then, the damage may be irreparable.

Can you clarify what you mean? It is included in the FileMaker Developer Subscription. While I can't speak for you, I know the DMT tool alone has saved me significantly more than $99 worth of time.

What version of FileMaker are we talking about here? Your profile says '11 Advanced', your question references "FileMaker Pro 9". Either of those versions are really old... that may be the reason. Also keep in mind that sometimes ( a lot of the time ) the syntax of the commands are case-sensitive. Make sure that is correct. Next: If you paste the text of the command you are trying to run in the command line, does it work? Ultimately, FileMaker just hands off the command to the operating system, so there is not a lot of complexity in that leg of the action. Can you give us a sample of what the argument looks like? What are you expecting the action to do? You mention the path of the script to run, and you mention what shows up in the cmd window, but don't tell us if that is right, wrong, or no related.

How consistent is the input? is 'posterOffset' always after the 'value"? are there ever double quotes inside of the value itself? There are several ways to do this, and I know others will pop in with some excellent suggestions. They may range from finding the beginning and end of the 'value' portion of the text, to looping through each character to be more dynamic in figuring out where the end of that string is. The answers to the above questions may help other decide which type of solution to provide.

It's probably going to end up hurting you down the road to try and do this with ExecuteSQL. That's not really what the function was intended for, and can have some serious performance degradation under specific circumstances. There are several ways to accomplish what you want to do. Take a look at this and see if it helps. Also, take some time to run through the courses on the Claris Academy. They will help fill in some blanks about features available in FileMaker for this type of thing. https://support.claris.com/s/article/Simple-example-of-a-subsummary-report-1503692935845?language=en_US

Over WAN, having the JSON already set can often create a significant performance increase on complex JSON. When I can, I'll actually push this to a separate table, if it's in a system or file that I already have handling CRUD operations with a transaction. It's part of an overall development pattern. With that, it can be easily used with script parameters, external APIs, scripts, calculations, error trapping, etc. It is all about controlling WHEN the user has to wait for the actions to happen. If I can, without compromising data integrity, have those actions happen when the user is sleeping, that's the route I go. Forcing a wait time when the user expects there to be a wait is ideal.

I absolutely do. There are options once you click buy. I agree, it's not a very intuitive design.

Why is it embarrassing? They are two very different things. At the very least, it's a one-time purchase vs a monthly subscription.

The reference in the help documents about the script step not being compatible means that it wasn't tested to work, or you will experience issues, not necessarily that it would never function at all. As you have found, it may or may not work without warning.

https://www.elemental-fm.com/ Also lots of places to get them, but these ones are already set to work with FileMaker.

Just note that Google has deprecated that option. So I wouldn't put too much time into building your features based on that option. In most GSuite accounts, it's already disabled.

OAuth isn't quite as easy as flip on an option. At least not when you are dealing with sending email. Your next option then, is to have your clients set up an app password. You will be responsible for securing it if you store it. This is better than storing the user's actual account password, but will require some diligence on your part to make sure no can get direct access to that password. https://support.google.com/accounts/answer/185833?hl=en

18 will not be able to connect to FileMaker Server 15 either. https://support.claris.com/s/article/System-Requirements-for-FileMaker-Pro-18-Advanced?language=en_US About half way down are the versions it can connect to.

It is a security change with Google, and Gmail. You need to either authenticate with OAuth, or use an App Password. The user has to set up the App Password to use with their account. We recently experienced the same thing. If your clients have a business account with google, they can setup the SMTP relay and use that, by allowing only their IP addresses to send email.

If you use a path like @comment pointed out, it will work. I typically use a custom function for this process that handles the path for me, and I neglected to show the adjustment to the path. But it does work with that path he showed. "file:///" & Let ( [ path = Get ( DocumentsPath ) ; transformPath = Substitute ( Get ( DocumentsPath ) ; "/" ; "¶" ) ; listCount = ValueCount ( transformPath ) ; adjustedList = MiddleValues ( transformPath ; 3 ; listCount - 2 ) ; newPath = Substitute ( adjustedList ; "¶" ; "/" ) ; result = newPath ] ; result ) & "fileName.pdf"