Updated XMLMapper

[Roger Cigol 131]

Hi @MrBlues I do wonder if you might have been better posting your question as a brand new topic rather than adding it on the end of a year old and only partially related post. Not to worry....

 

It is always better to start with a *.xsd schema file rather than an *.xml data file when creating transformations. The schema can (and usually does) contain more information about fields.

However not every use case allows this (a schema may not exist or may not be available) and XML mapper is designed to work when you start with an XML data file (as you have done)

 

The main purpose of XML mapper is as a design tool. You create a dataset mapping and from this you create a transform file *.xtr,

The normal case is then to forget about XML mapper and just take your transform file and use this at run time in your Delphi (or C++) application.

 

If you load the transform file back into XML mapper it does not contain any data and you get the blank fields (exactly as you have described).

 

There are (rare?) cases where you want to load in the *.xtr transform file back into XML mapper (perhaps if you want to edit it, for example).

To do this you need to store a copy of the original XML data file in with the transform file, at the time the transform file was created.

This usually results in a much larger transform file and this "file size bloat" serves no purpose when the transform is used at run time in a

Delphi or C++ app.

 

For this reason XML mapper now has a check box that must be selected (before the transform file is created) that forces XML mapper 

to include the XML data file in the transform file. You can see this check box (called "Incl. XML Schema" on your first screen shot, towards

the bottom left of the middle section of XML mapper.

 

BACKGROUND: Earlier versions of XML mapper did not have this check box and always added the XML data to the transform file.