Resolve issue where User cannot see the entire structure of Data in EngageOne

Product Feature: Printing-General Output

Operating System: Windows 2008 64bit

Issue

Customer imported an xml file and was not able to view entire structure contained.

They are trying to set up a test case to Print and Archive and need to map data. They only see the “LEVEL1 parents".

In the data in DOC1 data layout they can see the entire structure of the data to all levels.

Cause

User is not able to map fields because data elements are not visible in EnagageOne.

Resolution

UPDATED: November 3, 2017
Checking the schema file in the template, it was noticed that schema file needs the other schema files as below:

<xs:import namespace="http://www.iinet.net.au/InvoiceManagement/Schemas/1.0/Customer.xsd" schemaLocation="./Customer.xsd"/> 
<xs:import namespace="http://www.iinet.net.au/InvoiceManagement/Schemas/1.0/Company.xsd" schemaLocation="./Company.xsd"/> 
<xs:import namespace="http://www.iinet.net.au/InvoiceManagement/Schemas/1.0/InvoiceDetails.xsd" schemaLocation="./InvoiceDetails.xsd"/> 
<xs:import namespace="http://www.iinet.net.au/InvoiceManagement/Schemas/1.0/IntegrationFault.xsd" schemaLocation="./IntegrationFault.xsd"/> 
On the other hand, those referenced schema files are not packaged in the template. So I assume that EnageOne doesn't support this format template.



Using external schemas is not supported by EngageOne and will not work, there are several issues at play here including publish, batch, performance, versioning, etc...

We investigated this to see if anything could be done but the solution is to use a single schema.