#Filemaker baseelements plugin pro#

Filemaker has a function called 'position'. I will then have to detect whether there is a '' defined. It is an array like node name that starts with '//'. To start off, I use the same convention of defining the Xpath.

#Filemaker baseelements plugin pro#

I don't have Filemaker Pro Advanced so cannot copy the custom function. It triggers my mind that I could use the same method to extract nodes. I tried as far as possible to avoid using 'Evaluate' thus do not want to use it.įortunately, two of the scripts uses the same functionality provided by Andy Knasinsky (). It may be due to efficiency, they try to use as little script steps as possible to achieve results. There are some but its codes are a bit too complicated to comprehend. I tried to lookup for scripts that is available in the internet. Filemaker Go does not have the capability to use Plugins. Moreover, the script needs the BaseElements plugin. It ended up that I have to check whether there is multiple node of the same name by trying to parse '//mynode' first to see it has a value then go to the appropriate routine to extract the single or multiple nodes. However, if the XML returned can be one or more nodes of the same name, it is an issue. If the XML format is always constant, there is no problem. You must use a array style like '//mynode' to get the correct value.

If there is multiple nodes with the same node name then it is a issue. If there is only one node with a specific node name, it can easily be extracted by using '//mynode'. But due to its functionality, BE_Xpah treats nodes differently. Normally, I would use BaseElements plugin function BE_XPath to do the node extraction.

Filemaker does not have functions that handle XML in variables. While doing communications with Apple GSX, I have to constantly receive XML from GSX.