Skip to main content
Nintex Community Menu Bar
Solved

Load Repeating section content to SQL


Forum|alt.badge.img+2

HI, Nintex Experts 

A very Good Morning from Nepal, 

I'm attempting to use a Sharepoint Nintex List workflow to insert data from a repeating section of a form into multiple rows in a SQL table. For instance, if the repeating section contains multiple values, I want to insert each of those values into a separate row in the SQL table along with the Unique ID 

In below i am trying to insert each filled shift and roster date in SQL. 

 

Any Help and suggestion will be greatly appriciated.

 

 

Best answer by SimonMuntz

Hi @jajwalya,

Welcome to the Nintex forums and a great question for an interesting solution.

The output of a repeating section control is XML.
The first thing to do is to create a column in your list that is Multiple lines of text configured as plain text.
Your repeating section control on your form is connected to this column.

The workflow will have to loop through each row of the XML and add it to your database.
Below is a basic workflow that can achieve the solution.
I've attached the workflow, form ,and list template.
You will need to add your connection string in the Execute SQL action and enter the correct column names for your DB.
 

 

View original
Translate
Did this topic help you find an answer to your question?

6 replies

SimonMuntz
Nintex Employee
Forum|alt.badge.img+22
  • Nintex Employee
  • 2437 replies
  • Answer
  • August 22, 2024

Hi @jajwalya,

Welcome to the Nintex forums and a great question for an interesting solution.

The output of a repeating section control is XML.
The first thing to do is to create a column in your list that is Multiple lines of text configured as plain text.
Your repeating section control on your form is connected to this column.

The workflow will have to loop through each row of the XML and add it to your database.
Below is a basic workflow that can achieve the solution.
I've attached the workflow, form ,and list template.
You will need to add your connection string in the Execute SQL action and enter the correct column names for your DB.
 

 

Translate

Forum|alt.badge.img+2
  • Author
  • Rookie
  • 6 replies
  • August 25, 2024

Thank you Very Much SimonMuntz it worked fine for me. I have tried both in sharepoint list and SQL. also i want your additional suggestion, is there any way to optmize the process time as its taking 5-8 second to run. 

 

Translate

Forum|alt.badge.img+2
  • Author
  • Rookie
  • 6 replies
  • August 25, 2024

and also i been trying to do same process in Nintex Site workflow. if there any refference it will be great help and also thanks is advance. 

Translate

SimonMuntz
Nintex Employee
Forum|alt.badge.img+22
  • Nintex Employee
  • 2437 replies
  • August 25, 2024

Hi @jajwalya,

This question was posted in the Nintex for SharePoint section of the forum, which is for on-premise.
Based on your screenshot, you are using Nintex for O365, so I have moved this post to the correct section.

Nintex for O365 uses SharePoint Online’s workflow engine. To add capabilities, Nintex calls out to the Nintex infrastructure to perform some actions. The query XML action is one of those, which can add some time to the action's execution.

 


 

Translate

Forum|alt.badge.img+2
  • Author
  • Rookie
  • 6 replies
  • August 26, 2024

Thank you SimonMuntz for your prompt reply but we are not using Office 365 we are using on prem Sharepoint and On prem Nintex add on solution. and all server are configured as per sharepoint required architicuter.

Translate

SimonMuntz
Nintex Employee
Forum|alt.badge.img+22
  • Nintex Employee
  • 2437 replies
  • August 26, 2024

Hi @jajwalya,

Nintex for SharePoint, also uses SharePoint’s workflow engine, so Nintex can only run as fast as your environment.
Indexing the database table where the items are being created may speed things up.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings