Creating a record reference by importing a schema

, ,
1

Often when I import a schema I get a record reference that contains the root tag such as:

Invoice
->InvoiceHeader
->InvoiceDetails

So when you open up the record reference in a flow, you have the IData record with a name of Invoice and then the child is also Invoice. Is it preferable to omit this root IData record and use the record reference itself as the root element or to keep the repeated IData record? If we look at a pipeline variable called Invoice we would have:

Invoice (pipeline variable)
->Invoice
–>InvoiceHeader
–>InvoiceDetails

Thx
JB

2

Invoice (pipeline variable)
->Invoice
–>InvoiceHeader
–>InvoiceDetails

This should’nt cause any problem in the flow and output.