Cannot Delete Column in Scoped Application Table

[jmiskey]

I created a scoped application in our Dev environment in which we created some of our own custom tables in.   We then installed this application in our Test environment.

I went back and updated one of our custom tables in this scoped application.   Basically, I added a new column, and deleted an old one.

I then pushed the updates (via "Make App available to other instances"), and ran the update in our Test environment.

It successfully added my new table column, but did not delete the other one.   So I went directly into the table to delete it manually, but this option is not presented to me (I confirmed that I am in the correct application).   There is no Delete button, nor can I select the check box next to the Column names to select/delete it.

I have found a few threads that discuss issues such as these:

delete column on custom table?

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

Though, they are not exactly the same (the one talked about a custom column on a global table, and Helsinki patch 6 is mentioned).   We are on Helsinki path 9.

Is this still a problem in Helsinki patch 9?

When we go to roll out this into Prod, where we install it from our Dev environment (in which we successfully deleted it out of there), will it have the bad column in there or not?

Thanks

[jmiskey]

Thanks Chuck.

I wasn't sure if I should do that, because while it is a good work-around, it doesn't really allow me to delete the fields (which was the original question), and thought that if I leave it open, maybe someone knows a way in which I can delete it and will post it (but if it is mark it as resolved, there probably isn't much of a chance of that happening).   But if you are confident that there are no other ways at this time, I can do that.

(I am also fairly new to ServiceNow and these forums, so want to make sure that I follow proper protocol.)

[Chuck Tomasi]

Hi Joe.

I'm certain there is no way at the time (Istanbul or earlier) to push the field deletions from dev to another instance.

Good check on the protocol thing - very admirable. We did an episode of TechNow on this last year. You can always review that. Check out episode 27. TechNow Episode List

[jmiskey]

Thanks.

It doesn't necessarily have to be a deletion that is pushed from one environment to another (how it gets deleted isn't my main concern, just getting it deleted is).   I think your Update Set idea is a good one, and I wish I could try it, but am hesitant to do so because of all the other stuff wrapped up in that Update Set and all those error warnings.

I will check out that episode, thanks!

[Patrick Schulte]

Probably the easiest way is to use the dropColumn function of GlideSystem like this:

gs.dropColumn('tableName', 'columnName');

You could run this single statement in the Xplorer, as Fix Script or Background Script for instance.

[Ramiro Rincon B]

^ This is the way (For future readers, make sure you're in global)

Thank you, man! This worked like a charm.

I'm also an advocate of deactivate things, but there are some stuff that need to be wiped out.