|Mac & Win
Imports XML and creates tables, fields and records.
|The XML data to import.
|The file name of where the insert table is inside.
|The prefix to put in front of all tables.
|Sum of flags.
Add 1 to ignore errors in xml and continue parsing.
Add 2 to ignore outer XML wrapper nodes.
Add 4 to import flat, so no subtables for included nodes.
Add 8 to convert CDATA to text nodes. CData should contain ASCII or UTF-8 text!
Add 16 to trim values.
Add 128 to skip table creation (since v12.3).
Add 256 to skip field creation (since v12.3).
Add 512 to ignore duplicate errors for FileMaker's validation (since v13.5).
Add 1024 to not create UUID fields (since v13.5).
Returns number or error.
DescriptionImports XML and creates tables, fields and records.
This function can import any XML into FileMaker tables with all fields and attributes.
Returns number of records to be added. This function prefers the import and runs it later at idle time. In a script please call XML.Import and then loop and do script pauses. Then use XML.Import.Status to check regularly for updates. When you get back Finished as status, the script can continue with other work.
If you have a XML file you need to import regularly into FileMaker and you have no XSLT to transform it for FileMaker, you can use this plugin function. On the first run, it creates for a sample xml file the required tables and fields. Then you can define any layout or script to process values, e.g. copy into your tables. On further runs the plugin may add more fields (if newer xml file has more fields) and import newer records.
All tables have three default fields. _RecordUUID is a unique identifier for the record. _ParentRecordUUID provides a link to the record one level higher in the XML. This can be used to find child/parent records. The _CreationTimeStamp is the creation date, so you can distinguish different imports.
As a lot of records with a lot of data is imported and you may not need everything, you may want to put the imports in an extra FileMaker file. You decide if you clear tables before import or you want to keep history of all imports.
If the XML has errors like a missing < in the xml, you get an error. If you switch on IgnoreError parameter, the plugin reads everything until the error is reached which may give less records than possible.
This function works at idle time which is not supported on server. But you can use the function XML.Import.Work to perform the work instead of the idle handler. This enables importing of data, but not table/field creation.
Requires FileMaker 12 or newer.
See also XML.Import.SetBaseFields and XML.Import.SetExtraField.
We use SQL to create records, so you can check FM.ExecuteSQL.LastErrorMessage and FM.ExecuteSQL.LastSQL after the import for SQL errors.
Please wait for an import to finish before calling JSON.Import or XML.Import again since it will cancel the last import and start a new one.
Import fails if a table or field name matches a reserved word in FileMaker like RowId. Please rename entries if needed.
Since v13.5 you can explicit ask the plugin to not create UUID fields with the flag value 1024. Be aware, that this prevents us from giving you structural data like which child record belongs to which parent. But your import data may already have primary keys for this. Add flag 512 to ignore duplicate errors in FileMaker's field validation. This is useful if you mark some field as unique in FileMaker with always validation and import the same data again.
Imports test.xml into FileMaker:
Import script with progress bar for importing XML with Windows ANSI encoding:
Read Database Design Report:
Explicit import with passing database filename:
- Version 13.5
- Added new flags 512 to ignore duplicates (with FileMaker's validation) and 1024 to not create UUID fields to XML.Import and JSON.Import functions.
- Added XML.Import.GetExtraFieldDefinitions and XML.Import.SetExtraFieldDefinitions functions to create custom fields.
- Fixed XML.Import.ErrorCount and XML.Import.Errors to work better.
- Version 12.4
- Version 11.4
- Fixed an issue with XML.Import not parsing huge XML files with big text nodes correctly.
- Version 11.3
- Version 9.3
- Version 9.1
- Changed XML.Import to ignore BOM character.
- Version 8.5
- Improved XML.Import to better detect lists of XML nodes.
- Version 7.5
- Fixed problem with XML.Import and CData nodes.
- Version 7.1
- MBS Plugin 13.5 for Claris FileMaker
- MBS FileMaker Plugin, version 13.5pr7
- MBS Plugin 12.4 for Claris FileMaker
- The magic of our XML.Import function
- FileMaker 19.2 and the new fmplugin extended privilege
- MBS FileMaker Plugin 7.1 - More than 4400 Functions In One Plugin
- MBS FileMaker Plugin 5.4 for OS X/Windows
- JSON Import for FileMaker
- [ANN] MBS FileMaker Plugin 5.3 for OS X/Windows
- XML Import for FileMaker
This function checks for a license.
Created 8th September 2015, last changed 27th October 2023