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

[Chuck Tomasi]

Hi Joe,

When you publish your app, it doesn't do delete operations. There's a reason that the developers told me (and it made some sense at the time.) Once it is out of dev, the app record knows it's not on dev and that development should only be done in dev so it doesn't let you delete it manually in test or prod.

What you could try is the old school way. Go to the application record (sys_app) and publish to an update set, then retrieve, preview, and commit the update set on the test system and see if the DELETE operation comes through that way.

[jmiskey]

Thanks for the reply.

When I Preview the Update Set, it says it found 14 errors.   Is there a way to strip out just the one or two Delete Actions I need to run and just try running them?

[Chuck Tomasi]

Update sets are meant to be applied as a single unit. There is no picking and choosing of what gets applied on an update set for dependency reasons (e.g. you could end up making a change that depends on something that is not there.)

[jmiskey]

Based on all the error messages I got when previewing it, I am a bit hesitant to apply the whole Update Set.   I am worried it could end up doing more harm than good.   Most of these changes we have been applying through Application Updates (it is a scoped application), except for some global Client Scripts, Business Rules, and Workflows that we added to both environments manually.

It really isn't that big of a deal.   It isn't hurting anything it is there.   Just trying to clean up a bit of the old "garbage" to make it look a little cleaner.   When this gets applied to Production, it hopefully will not be there, since the environment that it will be moved from (Dev) does not currently have it in there.

Thanks