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

Document Generate Form - "Custom Table" fields and mapping to document attributes

  • February 13, 2025
  • 4 replies
  • 48 views
J
Newcomer
Forum|alt.badge.img+1

Hi,

I’m hoping someone might have come across a solution to the problem I’m trying to solve.
I have a document generation form, where one of the fields is a “Custom Table”. The table consists of two columns, with a date fields in the first column and a number field in the second column.

When completing the form, you can add multiple rows, so therefore the submitted “Params” XML data for this field contains a “Container” node, with a XML node for each row with a date value and a number value.

Within a CLM workflow, I’m trying to map the submitted data for this field to a document attribute. If I map the “Params” XML data’s “Container” node to a variable, it just saves as a raw ‘non’ delimited list of values from all the fields in the table, which is unusable. Can I iterate over the rows in the table’s XML data and save to separate attributes? 

Or is there another approach?

Any advise would be appreciated.

 

Thanks,

Josh

Best answer by Pawan Gangwani

Hello ​@jmillard 

I got it, I will try to explain how to achieve it in Workflow.

1. Open the attribute group and make those 2 attributes as a “Repeatable”.
2. Now open the Workflow and create one variable with “iterator” type variable coz we are going to use loop for this.
3. Then in “find iterator’ save the table from params.
 

  1. after saving it. using “For Each Loop” and select that iterator variable.
     
    1. Now bring “update variable value” step, refer ss:


       

    2. then use “Update document meta data” and refer the SS below.
       

      That’s the result,

       

      Hope this helps🫡

View Original
Is this content helpful?

4 replies

Pawan Gangwani
Rising Star
Forum|alt.badge.img+13

Hello ​@jmillard 

Welcome to the DocuSign Community!

After reading it, I understood that you want to update the table data into the attributes, is that right? and separate attribute means that, is same table row contains 2 different options that both should be updated separately in attributes? 

Way to Learn | I'd love your feedback | Hit Like | Mark it Best🌈
J
Newcomer
Forum|alt.badge.img+1
  • jmillardNewcomer
  • Author
  • Newcomer
  • 2 replies
  • February 20, 2025

Hi ​@Pawan Gangwani,

Thanks for your reply. 

Yes, I’d like to take the table data, which could consist of 1+ rows with two values per row (Date and Volume). Then save this data against a document attribute or separate attributes. But as the number of rows added during the completion of the document generation form is unknown (Controlled by the user) I think simply saving the ‘raw’ XML from the custom table to a single document attribute will be sufficient, but when I try to save the XML to a ‘String/Text’ attribute it saves as a raw ‘non’ delimited list of values rather than the XML mark-up. Which is un-useable.

 

Hope this makes sense.
Thanks,

Josh

Pawan Gangwani
Rising Star
Forum|alt.badge.img+13
  • Pawan GangwaniRising Star
  • Rising Star
  • 401 replies
  • Answer
  • February 20, 2025

Hello ​@jmillard 

I got it, I will try to explain how to achieve it in Workflow.

1. Open the attribute group and make those 2 attributes as a “Repeatable”.
2. Now open the Workflow and create one variable with “iterator” type variable coz we are going to use loop for this.
3. Then in “find iterator’ save the table from params.
 

  1. after saving it. using “For Each Loop” and select that iterator variable.
     
    1. Now bring “update variable value” step, refer ss:


       

    2. then use “Update document meta data” and refer the SS below.
       

      That’s the result,

       

      Hope this helps🫡

Way to Learn | I'd love your feedback | Hit Like | Mark it Best🌈
J
1 person likes this
  • J
    jmillard
J
Newcomer
Forum|alt.badge.img+1
  • jmillardNewcomer
  • Author
  • Newcomer
  • 2 replies
  • February 21, 2025

Thanks so much ​@Pawan Gangwani 
That did the trick! I’ve got it working now.

Appreciate your time in creating a detailed explanation.

 

Cheers,

Josh

Reply


Most helpful members this week

Code of Conduct

Docusign Community

Code of Conduct