Skip to main content
arrow-left Back to Docusign.com
Solved

Table population from csv file CLM

C
Newcomer
Forum|alt.badge.img+2

Dear All,

I hope somebody can help, I am trying to setup a table in CLM where the user will have certain options to choose from depending of the csv file that we have created. 

When testing it I notice when just one selection has been made in the table it is all working

 

 

when adding a second row I get the following error:

 

I am not sure on how to solve this the merge tags that I have are 

<# <TableRow Select="//Aanvulling_tot" /> #>

<# <Content Select="//Group_of_Products_Aanvulling" Optional="true"/> #>

<# <Content Select="//Product" Optional="true"/> #>

<# <Content Select="//Addition" Optional="true"/> #>

<# <Content Select="./Aanvulling_tot_percentage" Optional="true"/> #>

 

I have added the csv and the word table for document creation.

thanks in advance,

best regards,

Casper

 

 

 

Best answer by Kelly.Gatling

Hi Casper! Welcome to the Docusign Community! 

This may be an issue of using the incorrect xpath in your merge tags. The above tags contain absolute // whereas for table and repeating data, you should be using relative ./ 

You can read more about absolute versus relative xpath here: https://support.docusign.com/s/document-item?language=en_US&bundleId=uqj1643324072491&topicId=uno1576795541214.html

 

 

<# <TableRow Select="//Aanvulling_tot" /> #> - This is correct. The TableRow tag uses absolute //. 

 

For the other Content tags, try changing to: 

<# <Content Select="./Group_of_Products_Aanvulling" Optional="true"/> #>

<# <Content Select="./Product" Optional="true"/> #>

<# <Content Select="./Addition" Optional="true"/> #>

 

The only difference is that these updated tags contain relative xpath ./ versus absolute //. 

Hope this helps!
Kelly

View Original
Is this content helpful?

3 replies

Justin Jiang
Digital Collaborator
Forum|alt.badge.img+11
  • Justin JiangDigital Collaborator
  • Digital Collaborator
  • 205 replies
  • May 1, 2024

I configure csvs in forms in document generation

Welcome to the DocuSign Community and University! Your feedback is immensely appreciated. If this answer resolves your issue, please feel free to give it a Like and mark it as the "Best Answer". This helps others in the community find the information they need. Visit us at http://dsucustomers.docusign.com for more resources and support.
K
Docusign Employee
Forum|alt.badge.img+6
  • Kelly.GatlingDocusign Employee
  • Docusign Employee
  • 35 replies
  • Answer
  • May 6, 2024

Hi Casper! Welcome to the Docusign Community! 

This may be an issue of using the incorrect xpath in your merge tags. The above tags contain absolute // whereas for table and repeating data, you should be using relative ./ 

You can read more about absolute versus relative xpath here: https://support.docusign.com/s/document-item?language=en_US&bundleId=uqj1643324072491&topicId=uno1576795541214.html

 

 

<# <TableRow Select="//Aanvulling_tot" /> #> - This is correct. The TableRow tag uses absolute //. 

 

For the other Content tags, try changing to: 

<# <Content Select="./Group_of_Products_Aanvulling" Optional="true"/> #>

<# <Content Select="./Product" Optional="true"/> #>

<# <Content Select="./Addition" Optional="true"/> #>

 

The only difference is that these updated tags contain relative xpath ./ versus absolute //. 

Hope this helps!
Kelly

Kelly Gatling | Principal Product Trainer | Docusign University
C
1 person likes this
  • C
    Casper Tukker
C
Newcomer
Forum|alt.badge.img+2

Thanks Kelly, I have created the table again and now get the dots in my merge tags. 

Not sure why the where not generated like that in previous table.

best regards

Casper 

K
1 person likes this
  • K
    Kelly.Gatling

Reply


Most helpful members this week

Code of Conduct

Docusign Community

Code of Conduct