XML - Possibility of Excluding the HMTL Tags

[RSCCITeam]

Good day, Is anybody able to assist, We've got a 3rd party company that wishes to integrate the Appsheets entries into their software, but requires it in XML format.

We've setup the template to match theirs, however when the XML file gets generated it has HTML formatting at the top that makes the XML file impossible for them to read.

Actual Output of XML File:

XML with HTML Formatting

Template setup in Appsheets:

Template setup in Appsheets

[SkrOYC]

Please share your Automation Task config

[RSCCITeam]

Template:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<events:LOGISTICS_ORDER_EVENT_MSG xmlns:core="http://system.mp-objects.com/schemas/MTC/MTCCore/V1/MTCCore.xsd" xmlns:events="http://system.mp-objects.com/schemas/MTC/LogisticsOrder/V1/LogisticsOrderEvent.xsd">

<events:header>

<core:typ>LOGISTICS_ORDER_EVENT_MSG</core:typ>

<core:mid></core:mid>

<!--  unique value for the message, if this is not possible, then RSC should keep the segment emtpy.  -->

<core:ver>1</core:ver>

<core:mode>P</core:mode>

<core:ack>NE</core:ack>

<core:cre> <<[End Timestamp]>> </core:cre>

<!--  Creation date time of the message -->

<core:sap>RSC</core:sap>

<!--  Here the Sending system name should be, in this case RSC -->

<core:rap>DSVFMS</core:rap>

</events:header>

<events:body>

<events:LOGISTICS_ORDER_EVENT>

<events:PROCESSING_DETAILS>

<core:PURPOSE_CODE>00</core:PURPOSE_CODE>

</events:PROCESSING_DETAILS>

<events:EVENT_IDENTIFICATION>

<core:VALUE> <<[Trip Number]>> </core:VALUE>

<!--  Here the service order number from the Loading service order should be given  -->

<core:QUALIFIER>EVENT_TRACKING_REFERENCE</core:QUALIFIER>

</events:EVENT_IDENTIFICATION>

<events:EVENT_IDENTIFICATION>

<core:VALUE>LOADING</core:VALUE>

<core:QUALIFIER>SERVICE_ORDER_TYPE</core:QUALIFIER>

</events:EVENT_IDENTIFICATION>

<events:EXECUTED_BY>

<core:PARTY_ID>passthrough</core:PARTY_ID>

<core:ORGANIZATION_ID>RSC_DSVPLUMBAGO</core:ORGANIZATION_ID>

<!--  Fixed value, this can change if in the future more yard management will be connected to this -->

</events:EXECUTED_BY>

<events:EVENT_TYPE>ARRIVAL</events:EVENT_TYPE>

<!--  Two values possible: ARRIVAL for truck arrival and DEPARTURE for truck departure -->

<events:EVENT_DTM> <<[Truck Arrival Time]>> </events:EVENT_DTM>

<!--  Date and time of the event (truck arrival or truck departure  -->

<events:EVENT_VALUE>

<!--  Extra information can be given as event values if they are available. Just repeat the whole Event value segment. How ever qualifiers needs to be agreed upfront -->

<core:VALUE> <<[Truck Registration]>>  </core:VALUE>

<core:QUALIFIER>LICENSE_PLATE</core:QUALIFIER>

<!--  available values: LICENSE_PLATE, CARRIER_NAME, DRIVER_MOBILE, LAST_NAME, FIRST_NAME, RECIPIENT,   -->

</events:EVENT_VALUE>

<events:EVENT_VALUE>

<core:VALUE> <<[Driver Name]>> </core:VALUE>

<core:QUALIFIER>DRIVER_NAME</core:QUALIFIER>

</events:EVENT_VALUE>

<events:EVENT_VALUE>

<core:VALUE> <<[Container Number]>> </core:VALUE>

<core:QUALIFIER>CONTAINER_NUMBER</core:QUALIFIER>

</events:EVENT_VALUE>

</events:LOGISTICS_ORDER_EVENT>

<events:LOGISTICS_ORDER_EVENT>

<events:PROCESSING_DETAILS>

<core:PURPOSE_CODE>00</core:PURPOSE_CODE>

</events:PROCESSING_DETAILS>

<events:EVENT_IDENTIFICATION>

<core:VALUE> <<[Trip Number]>> </core:VALUE>

<!--  Here the service order number from the Loading service order should be given  -->

<core:QUALIFIER>EVENT_TRACKING_REFERENCE</core:QUALIFIER>

</events:EVENT_IDENTIFICATION>

<events:EVENT_IDENTIFICATION>

<core:VALUE>CONTAINER</core:VALUE>

<core:QUALIFIER>SERVICE_ORDER_TYPE</core:QUALIFIER>

</events:EVENT_IDENTIFICATION>

<events:EXECUTED_BY>

<core:PARTY_ID>passthrough</core:PARTY_ID>

<core:ORGANIZATION_ID>RSC_DSVPLUMBAGO</core:ORGANIZATION_ID>

<!--  Fixed value, this can change if in the future more yard management will be connected to this -->

</events:EXECUTED_BY>

<events:EVENT_TYPE>LOAD_START</events:EVENT_TYPE>

<!--  Two values possible: ARRIVAL for truck arrival and DEPARTURE for truck departure -->

<events:EVENT_DTM> <<[Loading Start Time]>> </events:EVENT_DTM>

<!--  Date and time of the event (truck arrival or truck departure  -->

</events:LOGISTICS_ORDER_EVENT>

<events:LOGISTICS_ORDER_EVENT>

<events:PROCESSING_DETAILS>

<core:PURPOSE_CODE>00</core:PURPOSE_CODE>

</events:PROCESSING_DETAILS>

<events:EVENT_IDENTIFICATION>

<core:VALUE> <<[Trip Number]>> </core:VALUE>

<!--  Here the service order number from the Loading service order should be given  -->

<core:QUALIFIER>EVENT_TRACKING_REFERENCE</core:QUALIFIER>

</events:EVENT_IDENTIFICATION>

<events:EVENT_IDENTIFICATION>

<core:VALUE>LOADING</core:VALUE>

<core:QUALIFIER>SERVICE_ORDER_TYPE</core:QUALIFIER>

</events:EVENT_IDENTIFICATION>

<events:EXECUTED_BY>

<core:PARTY_ID>passthrough</core:PARTY_ID>

<core:ORGANIZATION_ID>RSC_DSVPLUMBAGO</core:ORGANIZATION_ID>

<!--  Fixed value, this can change if in the future more yard management will be connected to this -->

</events:EXECUTED_BY>

<events:EVENT_TYPE>LOAD_End</events:EVENT_TYPE>

<!--  Two values possible: ARRIVAL for truck arrival and DEPARTURE for truck departure -->

<events:EVENT_DTM> <<[End Timestamp]>> </events:EVENT_DTM>

<!--  Date and time of the event (truck arrival or truck departure  -->

</events:LOGISTICS_ORDER_EVENT>

<events:LOGISTICS_ORDER_EVENT>

<events:PROCESSING_DETAILS>

<core:PURPOSE_CODE>00</core:PURPOSE_CODE>

</events:PROCESSING_DETAILS>

<events:EVENT_IDENTIFICATION>

<core:VALUE> <<[Trip Number]>> </core:VALUE>

<!--  Here the service order number from the Loading service order should be given  -->

<core:QUALIFIER>EVENT_TRACKING_REFERENCE</core:QUALIFIER>

</events:EVENT_IDENTIFICATION>

<events:EVENT_IDENTIFICATION>

<core:VALUE>LOADING</core:VALUE>

<core:QUALIFIER>SERVICE_ORDER_TYPE</core:QUALIFIER>

</events:EVENT_IDENTIFICATION>

<events:EXECUTED_BY>

<core:PARTY_ID>passthrough</core:PARTY_ID>

<core:ORGANIZATION_ID>RSC_DSVPLUMBAGO</core:ORGANIZATION_ID>

<!--  Fixed value, this can change if in the future more yard management will be connected to this -->

</events:EXECUTED_BY>

<events:EVENT_TYPE>DEPARTURE</events:EVENT_TYPE>

<!--  Two values possible: ARRIVAL for truck arrival and DEPARTURE for truck departure -->

<events:EVENT_DTM> <<[Date Dispatched]>> </events:EVENT_DTM>

<!--  Date and time of the event (truck arrival or truck departure  -->

</events:LOGISTICS_ORDER_EVENT>

</events:body>

</events:LOGISTICS_ORDER_EVENT_MSG>

[SkrOYC]

Is your template an actual XML file in your GDrive?

[RSCCITeam]

I Selected Create on Appsheet which created the Google form, I then inputted the XML file formatting along with the <<[Fields]>> where I need them to populate for the other Software/App to import the data.

[SkrOYC]

Then try to have a manually created .xml file

[RSCCITeam]

How do I do a manual created? As I publish everything in the template.

I did a test and changed it to Json format which also generated to HTML text