This enables FileMaker to interact with a variety of web pages, and opens up interaction with REST-ful APIs. This data can consist of values like HTML, XML, JSON, and images. Once you run this script, the web page data loads into the specified field. With the “Insert from URL” script, it’s now possible to supply a URL in script and have it load the contents into a field.
#FILEMAKER SOAP USING BASEELEMENTS PLUGIN PRO#
In one instance where I needed geolocation information using Google’s KML, I had to resort to importing XML from a URL and parsing it with XSLT, a method that no longer works in FileMaker Pro 12. If you wanted to get XML from web pages, such as geolocation from Google or Yahoo pages, I discovered that the web viewers and XML were not ideal for cross-platform solutions, as it generally failed to provide the XML in a Windows environment. This usually meant loading a web page in the web viewer, using the function GetLayoutObjectAttribute inside a script to pull the HTML source (after waiting to make sure the page loaded all the way in the web viewer), and then parsing the HTML with text functions. In previous versions of FileMaker Pro, interacting with web sites to pull data required a method called web scraping.
One example of ExecuteSQL emerged at DevCon 2012: Inspector 4.0, a database analysis tool created in FileMaker, dropped the number of table occurrences from 626 to 135 and the number of relationships from 591 to 81, largely through the use of ExecuteSQL. Yet there is another feature of FileMaker Pro 12 with vast power, at least in terms of integrating with external applications: the “Insert from URL” script step.
When FileMaker Pro 12 launched earlier this year, it seemed that most attention centered on a new layout design surface and the ExecuteSQL function.
0 kommentar(er)
