Welcome to Community Week 2025! Join us to learn, connect, and be recognized as we celebrate the spirit of Community and the power of AI. Get the details  

Custom Field with no "u_" Prefix

Bradford Shelle
Kilo Guru

More for curiosity than anything, but has anyone ever created a custom field on a table, then stripped out the "u_" that the system puts in place to denote that the field was user generated?

1 ACCEPTED SOLUTION

Michael Fry1
Kilo Patron

If you could find a way to do so, I would advise against doing it. On the next upgrade, that field could get over written by mistake because it doesn't start with a 'u'.


View solution in original post

8 REPLIES 8

Michael Fry1
Kilo Patron

If you could find a way to do so, I would advise against doing it. On the next upgrade, that field could get over written by mistake because it doesn't start with a 'u'.


Mmmm fair point. That could go south quick on accident.


Hi,



Is this the same case with scoped applications. We have a scoped custom application and I notice the "u_" is removed before the column name.


Could this be a problem later being that it is a scoped application created in Studio?



Or is it OK to strip the "u_" in this case?



Thanks,



Tom


Scoped apps do not use the u_ prefix but instead us their own namespace identifier.