![how to search for a range of states in filemaker pro 10 how to search for a range of states in filemaker pro 10](https://www.mymac.com/wp-content/uploads/2020/06/HP8H2.jpg)
Continue reading “PSOS – Run Script in File not open Locally” → Tagged Perform Script on Server, PSOS 9 Comments JSON, Level: Advanced, Version: FM 19 or later FileMaker 19 + JSONata Fortunately there is a “c” option not mentioned above which I’ll get to shortly, but first let’s demonstrate the issue. Hmmm… I think we can agree that from a security standpoint “b” is a non-starter, and the whole point of this article is to avoid “a”. …in other words, if you want PSOS to be able to access files, you need to either a) already have the files open client side, or b) throw caution to the wind, and configure the hosted files to auto-open with pre-entered credentials. If we consult the online help entry for running scripts on server, the official word is that server-side scripts can access other FileMaker files only when… But of course there may be circumstances where you’d like to be able to access files server side that the user does not have open client side, either because the user’s credentials do not allow access to those files, or because you’d rather not have to open the files client side merely to facilitate a PSOS call.
![how to search for a range of states in filemaker pro 10 how to search for a range of states in filemaker pro 10](https://www.productivecomputing.com/wp-content/uploads/2020/10/FileMakerFundamentals-03.jpg)
Here’s the behavior, or misconception, actually: a server side script initiated via PSOS (apparently) cannot access files on the server unless the user already has those files open locally.
![how to search for a range of states in filemaker pro 10 how to search for a range of states in filemaker pro 10](https://m.media-amazon.com/images/I/81nszuyw10L._AC_US800_.jpg)
Today I want to take a look at a certain Perform Script On Server (PSOS) behavior, and for those who find this behavior to be inconvenient, propose a work around. Update: See Jason Wood’s suggestion in the comments section for making this technique more secure. Continue reading “JSONQuery, part 1” → Tagged Custom Function, JSON, JSONQuery, While 7 Comments JSON, Level: Intermediate, Version: FM 18 or later, Virtual List Virtual List Reporting, part 4 Typically you’re going to be feeding it a large JSON array you’ve received back from the FileMaker Data API, or somebody else’s API, where each record is a JSON object within a larger parent JSON array, and the purpose of this function is to be able to find child elements in that parent array that match certain criteria and return just those elements to you.Ībove and beyond that it has a lot of bells and whistles, some of which I’m sure we’ll cover, but the main impetus for writing it was giving you an easy and fast way to essentially query a JSON array.įor example, let’s say you have an array filled with a lot of orders, but you only need to get the order items that are being shipped to a certain city, or to a certain state, then this function would allow you to easily obtain those elements in an efficient manner. JSONQuery is a custom function, and it operates on JSON. I was wondering if you could start out with a brief description of what JSONQuery is?
![how to search for a range of states in filemaker pro 10 how to search for a range of states in filemaker pro 10](https://i.ytimg.com/vi/irw0PmJzuSM/maxresdefault.jpg)
You’ve been developing JSONQuery over the last few years, and today I have the honor of presenting and discussing it here with you on FileMaker Hacks. (Yes, it’s possible to accomplish the preceding with variables as well, but the aim here is to keep things simple).ĭemo file: connecting-portals-to-json-arrays.zipĬontinue reading “Connecting Portals to JSON Arrays” → 2 Comments JSON, Level: Advanced, Version: FM 18 or later JSONQuery, part 2ĭemo file: CF_JSONQuery_20211130_0120_ As you navigate from record to record within the demo, the portals will reconfigure themselves to accommodate the corresponding JSON.You will see changes made in the portal immediately reflected in the JSON, and vice-versa.(Why would you want to do this? One use case would be to provide dynamic scrollable selection criteria for a report.)Īt any rate, today we’re going to take a look at a little proof-of-concept I threw together to enable portals to display and edit data in JSON arrays. In a real-world implementation, the JSON would likely be sitting in a $$variable, which, among other things, would help make the technique multi-user friendly. Here, in the interest of simplicity, I’ve opted to store the JSON in a regular text field. Have you ever wished you could connect a portal to a JSON array? Portals and JSON arrays seem like they should be a natural fit, but FileMaker doesn’t offer us an obvious way to connect one to the other.