Solved

Repeating Section's column name issue

  • 1 November 2021
  • 6 replies
  • 4 views

I have an issue of Column Name in Repeating Section.

In Form, I create "Departure Country" in Repeating Section.

But after submitting it, it is recorded as "_bd44be4485249ec3c523b56708061cfa".

 

What is the solution for this issue?

icon

Best answer by nico 2 November 2021, 15:06

View original

6 replies

Userlevel 5
Badge +14

You likely just need to go into your Control's settings and give it a proper Control Name instead of just a label. 

1. What is "proper Control Name"?


2. What is "label"?

Userlevel 4
Badge +10

I imagine you mean the XML generated by the repeating section


 


It depends on the type of form.


If you use a Nintex New Responsive Form => this is normal, this is the current operation.


 


If you use Nintex classic form  and you have set a name of your control (name of the control in the Form designer) this should not happen.

Thank you, @nico 

Userlevel 5
Badge +14

Does Office 365's Responsive Form really behave differently from the On Prem on in this regard?

On Prim, all you need to do is to name the Control even in Responsive Forms for the XML to be correctly generated, just like Classic. 

Test Form with a Choice Control inside of a Repeating Section



 


Choice Control's Settings, showing the Control Name



 


Resulting XML from a test: 



 


 


is this different in 365? 

Userlevel 5
Badge +14

@youmatsu wrote:

1. What is "proper Control Name"?


2. What is "label"?




When you click on a Control that's on your form you'll see it's basic configuration open on the top ribbon, the "Control Name" I'm referring to is the "Name", and the "Label" is just called "Title" (which was my forgetfulness getting the better of me). 


 



(showing a control selected)


 



(showing the information on the top ribbon)


 


You can also double click on the Control and open the Settings of that Control, and you will find the same info: 



 


Setting that name should make the XML look a little more readable (assuming that Nintex roughly works the same in 365 land as it does On Premise):



 

Reply