Why does the Name of a String field changes to the system label in App Studio Form Designer?

[Paul A Ciocan]

I am learning through the Developer Learning Path and got to the Script Include exercise in Tokyo Release, where I need to add a String field.

After editing the Name automatically changes to the label of the string field, using underscores, which is not what normally should be doing. Also the Mandatory checkbox gets unchecked.

How can I overcome this issue?

I have attached a screenshot of it. Please see below.

[Anil Lande]

Hi,

Are you trying to modify existing field label? As per your screenshot page is read only. Can you please share all steps you have taken with screenshots?

Thanks,

Anil Lande

[Paul A Ciocan]

Hello Anil,

Well, I have taken the screenshots and here's what I am doing:

I open up the application NeedIt in the App Studio, head over the Forms and UI section and open the NeedIt form in Default View.

Then delete the already existing String field called Requested for Email, which isn't correct after previous attempt and save the form as it is.

Then I drag the new field to the corresponding place asked by the exercise, fill in the blanks with text, surprisingly it doesn't fill the Label automatically, I have to fill it myself. Then the 40 maximum limit and the Mandatory checkbox.

Then I save the form and the newly created field becomes read-only and misnamed.

Also, I tried both in Global and NeedIt app scope's, ended up with the same error.

What is wrong here? I am using the Tokyo Release by now.

Thanks if you can help.

[Yasser Al Kindi]

Hi Paul, hopefully you've sorted it by now. I had the same issue, only one of the field label and name were showing the same value u_requested_for. It must be a bug (I'm on San Diego), as I deleted it a few times and restarted - on the 4th attempt it just did what is expected. Sorry I dont have a solution as such!

[Paul A Ciocan]

Hi Yasser! I will try this way to retry multiple times, until it goes right, but I am using the Tokyo edition. Probably a bug, or my mistake on not updating to Tokyo release? I didn't check that yet. So, I'll check back yesterday.