Custom Field with no "u_" Prefix

[Bradford Shelle]

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?

[Pradeep Sharma]

I agree with Michael here, it is not recommended. This way you will find diffcult to differentiate between system n custom tables.

[Bradford Shelle]

Okay. I won't bother looking into it more since it sounds like it can create more problems than it will solve.

Thanks for the responses everyone!

[jijoesam]

I understand we may foresee few issues in the future after upgrades if we have custom fields without prefix 'u_'.

But if we create them as a part of a import set table otherwise any independent table, I am not sure how far an upgrade can impact.

If you still want to proceed, You can use the following script and run it from background or Fix Scripts.

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////

var attrs = new Packages.java.util.HashMap();

var fieldName = 'Name of the field';

var ca = new GlideColumnAttributes(fieldName);

ca.setType('string');

ca.setUsePrefix(false); // If you set this to TRUE, 'u_' will be added as prefix

attrs.put(fieldName, ca);

var tc = new GlideTableCreator('Table Name', 'Table Label');

tc.setColumnAttributes(attrs);

tc.update();

[Rajat Saxena]

Thanks for the solution. This worked quite well!!

Field is created but there is no way I could edit this field values now like type, length, label etc as it is now behaving as a system field.

Being an admin-still it is showing as insufficient rights to delete a field which I created as you mentioned.

Could you please help how could I update the field values or delete this field completely?