Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Why won't the system allow me to delete a scoped column on a global table

Community Alums
Not applicable

While editing my scoped application in the Studio, I added a Table Column to the Department table (cmn_department).   After changing plans, I no longer need that column.   There is no easy way to delete it that I can see.   So far, in testing on another instance, the only way is to do a GlideRecord delete with setWorkflow(false), but that makes me wonder why the system won't allow it.   Will it cause any problems with my scoped application if I force the deletion of the column?

1 ACCEPTED SOLUTION

chris_lo
ServiceNow Employee
ServiceNow Employee

Confirmed that this is a PRB (PRB690378) fixed in HP6. Support will have to delete this for customers who need the columns removed. This is for columns created on non-scoped tables.


View solution in original post

7 REPLIES 7

chris_lo
ServiceNow Employee
ServiceNow Employee

May have spoken too soon. I did some more testing and spoke with some colleagues and appears this would be a PRB. I'll update this thread on what I find.


chris_lo
ServiceNow Employee
ServiceNow Employee

Confirmed that this is a PRB (PRB690378) fixed in HP6. Support will have to delete this for customers who need the columns removed. This is for columns created on non-scoped tables.


All, the best practice is : Mark the column Active = False. That's it.