How to design template to show recurring data

If you are using a Table you can use the new TableRow tag to the root of your repeating XPath, if not using the old Repeat tags with the same Path will work. For the internal contents you will need your usually Content tags but the XPath will be relative to you TableRow or Repeat tag.

So:

<# <Repeat Select="//Locations_Container/Locations" Optional="true" /> #>

<# <Content Select="./Location_Name" Optional="false" /> #>

<# <EndRepeat/> #>

or

<# <TableRow Select="//Locations_Container/Locations" /> #> in any cell of the table row you want repeated

<# <Content Select="./Location_Name" Optional="false" /> #> in all other cells for content output

Where:

<Locations_Container>

<Locations>

<Location_Name />

</Locations>

</Locations_Container>

I used TableRow syntax and nothing was displayed on the document. Not sure what is wrong here...

here is the xml I am passing

  <Account>

  <Name>XYZ</Name>

  <Contact>

  <FirstName>John</FirstName>

  <LastName>Mack</LastName>

  </Contact>

  <Contact>

  <FirstName>Robert</FirstName>

  <LastName>Chang</LastName>

  </Contact>

  </Account>

I see extra spaces in your TableRow select.

Also, what exactly are you getting back, nothing as in blank or nothing as in not what you want?

I have one space between TableRow and Select and content comes blank in the document. Content should be populated with First Name and LastName in xml.

Removing the space makes TableRowSelect one word and I get error below.

To be clear I was stating the previous image showed extra spaces in your Select statement, not in the tag.

Finally I am able to generate the table with little tweaks in the definition.

Thanks for your inputs @Zakee Goliak​ 

Great job!

So, it looks like the extra spacing is gone, which I believe is the significant change.

The other change, //Contact, is a more direct pointer to the base of the repeat. I would caution that if in the future you XML structure changes, and Account becomes nested within another Repeat, this will throw an error stating there are more than one node for the requested path.

I understand your point on direct pointer but I was not able to give the xpath using nested nodes. I removed the spaces what you observed but the output was blank.

For now, I don't consider another level of nesting but thats the valid use-case for other workflow.

Another question, I think you might have answer. How can I add conditional logic to render the table? There is possibility that table data is not coming in the xml and tables not to be generated on the document not even a header? You have been helpful so far.