Custom field’s lost ‘u_’ or ‘x_’ prefix prefixes in scoped application

[kimaly]

We created scoped application in studio then we used form design to create some fields. The fields that I created starts with 'u_' prefix why is that? Shouldn’t have ‘x_’ prefix instead of ‘u_’?

Then wr created one more field using form layout and the field didn’t start with any prefix, why? I am afraid the field will be overwritten at next upgrade.

Is the ‘x_’ prefix for scoped tables only? Or it is for fields as well? Please let us know.

Thanks

Kim

[Michael Ritchie]

Form Designer is hard coded to add the u_ to fields created via that feature.  You can overwrite the field name when using it though.  Don't worry about upgrades because scope = customer defined table, fields, code etc.  The upgrade process isn't aware of custom code thus it will skip past it without knowing about it.  The only time an upgrade will affect a change is if you make an edit to an out of the box dictionary record or label.

But new fields in a scoped table does not put the u_ prefix by default.  They will have the scope prefix though behind the scenes.