I have created 3 new sections using section wizard and changed name of the UsrName field in all of them because I wanted different names.
But now whenever I publish any new object or compile items, I get this error. Is there any way to sort it out.
I am using demo environment.
Thank you
Like
Creatio does not like it when the UsrName is changed. You will need to change it back. You can change the title, but you cannot change the Name. You can, however, not use it. If you create a new String, you can change the Displayed Value in the Advanced Settings for the object to the new String you made. This changes the blue links to the new string instead of the UsrName.
Reid Burger,
Thanks for clarification.
I also would like to know if I can change the Required - At application level to No for UsrName.
RAMNATH SHARMA,
It is fine to change properties like required at application level to no. If the field is being used as the display value (like the name field) then having it blank would mean nothing would show in a lookup (if its used as a lookup somewhere).
BTW it's usually a good idea to not rename column or object names and only change the titles once they're created.
Ryan
Ryan Farley,
I changed back the names to UsrName using section wizard (which I later realized shouldn't have changed them back). Then I compiled the current workspace from Advanced settings to see if still any error occurs.
Here are some screenshots
Now The errors are because I changed back the name to UsrName, it says that the old Name - UsrClaimant don't exist.
I also opened the source code where these errors were pointing to -
But I can not edit the source code in Cloud demo instance.
Is there any way to change the source code or any process to correct these source codes?
Ramnath
Hi Ramnath,
As Reid mentioned, we do not recommend to change the name after the section being created.
If such an issue appears you can simply generate source code for all objects that are mentioned in compilation errors and compile modified items. If all necessary items were not removed this should fix the issue
Thank you.