[XML Records] Discussion

• The default null value for dates is the NullDate of the platform
• There is a new argument for the RecordListToXml and RecordToXml called DefaultConfig, where you can set if by default "Null values" are excluded and what is the default for child Recordlists

• ExcludeIfNull: when True, excludes elements that are empty in a structure, where empty means "equal to the NullableValue". The NullValue can be specified for each attribute if you like, but basically is 0 for numbers, NullDate() (1900/01/01) for Date, Time or DateTime attribues, and an empty string for every other attribute.
• RecordListMode: C or S (Child or Sequence). When you have a Record "Master" with an attribute "ChildList" that is a RecordList of "Child" Records, when RecordListMode is set to C the output will be something like <Master><ChildList><Child>...</Child><Child>...</Child></ChildList></Master>. When it is set to S, the output will be  <Master><Child>...</Child><Child>...</Child></Master> (ommits the parent element of the recordlist.

XMLConfig: It is a recordlist of RecordXmlConfig. It is basically an hashtable with a set of setting that you can add for specific Records. The record can be the name of the structure/record (in ou previous example "Child") or an hierarchical name ("Master/Child"). The extension, when serializing will look for the hierarchical name from bottom up. If it finds "Master/Child" it will apply those settings, if not, it will look for a "Child" config. If not found, it will use default settings. The settings list should be a list of records of type AttributeXmlConfig and each has the following attributes:

• Name: is the name of the attribute you are configuring
• AttributeName: If set it allows you to rename the attribute when exporting to xml
• ExcludeIfNull: Allows overriding the default ExcludeIfNull setting for the current attribute.
• NullableValue: Let's you tell that for the current attribute the nullvalue should be -1 instead of 0 for example.
• RecordListMode: Let's you set that on this specific attribute (in case it is a RecordList) what should be the export mode (Child or Sequence)

Hope this makes the settings a bit clear. Remember that you can use the extension itself to provide you thise settings filled from an XML:

Ex: Try calling the extension's XmlToRecordList of the following XML and use the result as the input for the DefaultConfig parameter

  <DefaultXmlConfig>

    <ExcludeIfNull>False</ExcludeIfNull>

    <RecordListMode>S</RecordListMode>

  </DefaultXmlConfig>

Regarding your question on base64: My suggestion is that you add an attribute of type Text to the structure you wish to export, then use the "BinaryData" extension to fill that attribute with the BinaryDataToBase64 result of your binary, and then just export the structure as usual with the RecordListToXml... Base64 is just binary data encoded as text, so it will be a normal attribute.

cheers,

Gonçalo

<?xml version='1.0' encoding='windows-1252'?>

Hi all,

Is there someone who can help me with the following? I am trying to generate KML files to be opened with Google Earth. I am using the XmlRecords extension to get this done. Hereunder you'll find a "Fraction of the expected output for the KML file".

The problem that I have now is that all Placemarks tags are appended to the first Folder instead of distributed over the 2 folders as shown below. Since I am using the ListAppend action while I am iterating to populate the structure and sub-structures (from which the KML file will be generated with the XmlRecords extension), I was wondering if there is a way (in the form of some sort of built-in action or extension) that I can use to go to the next row in the Folder-list and append the Placemarks to the correct Folder?

It might be handy to know (a portion of) the hierarchy of the structures that determines the layout of the resulting KML file:
<kml> - Main Record
 <Document> - Record
  <Folder> - Record List
   <Placemark> - Record List

Attached you'll find an oml-file with the logic in question. Note that the oml-file was created using Service Studio 5.1.

You're help will be much appreciated!

Regards,
Vernon

================================================
Fraction of the expected output for the KML file
================================================

  <Folder Id='Legend'>
   <name>Legend</name>
   <open>1</open>
   <Placemark>
    <name>color:#A1 92.1 dB(A)</name>
    <open>1</open>
    <styleUrl>#LegendIcon</styleUrl>
    <LineString>
    </LineString>
   </Placemark>
  </Folder>
  <Folder>
   <name>CPX Segments</name>
   <Placemark>
    <name>Segment 1: 92.1 dB(A)</name>
    <open>1</open>
    <LineString>
     <coordinates>52.1,5.1</coordinates>
    </LineString>
   </Placemark>
  </Folder>

• To always surround when exporting with a <RecordList> tag (this is the way .Net does for instance when you save DataSets to XML)
• To have an optional input on both actions that state the name of the root element? It would export normally and put a "<root>" element surrounding the items and ignore that when importing?
• To have some workaround to .Net's way of working so that we can read XML without a root element

Hi!
 

I have the following XML as the result of an external WebService call:

<WSNAME>
    <SUBMITSTATUS>Success</SUBMITSTATUS>
    <TABLE NAME="T1">
        <ROWSET>
            <ROW NAME="N1" VALUE="V1"></ROW>
            <ROW NAME="N2" VALUE="V2"></ROW>
            <ROW NAME="N3" VALUE="V3"></ROW>
        </ROWSET>
    </TABLE>
</WSNAME>

When I try to deserialize the XML to a RecordList everything is fine except for the attributes of the ROW nodes that are empty.
If I change the ROW nodes so thet they aren't empty (<ROW NAME="N1" VALUE="V1">.</ROW>) the ROW attributes return values

What I'm doing wrong?

Best Regards,
Luís Dias