Problems with update sets when uploading deleted data to another instance.

[Eloy3]

The problem is the following, in the development instance I created a table to use it in an import set (instead of creating it directly when configuring the import set) in such a way that I created a series of ACLs which I don't want and comparing with the rest of the tables created with an import set they don't have them. My question is if having deleted that table and those ACLs and other configuration that I will not need, to be all registered in the Update set, to upload it to another instance comes out a warning indicating that the references have been lost and so on, this affects the other instance storing junk records and things that do not interest us? And especially at the level of tables, having created it and then deleted and being registered in the update set even as DELETE is uploaded some kind of record or similar? Thank you very much

[DavyThoelen]

Hi @Eloy3 

Is your question about the error you get when you try to upload the update set to the other instance?

Or about the extra data that comes with it?

[Eloy3]

My question is if actually when uploading the update set to the production environment those records in the update set that appear with the DELETE action modify something in the production instance or not. And also to know if having created a table and then delete it in development, when uploading it to production that update set with table creation (and also deletion) can affect the maximum number of tables that can be created without cost?

[Danish Bhairag2 · Accepted solution]

Hi @Eloy3 ,

It wont have any impact though but the best practice would be not to move the deleted records in higher environment if it does not exist already in the higher environment. The deleted records you can move to the default update set of the respective application scope in lower/dev environment.

Mark my answer as helpful & accepted if it helps you.

Thanks,

Danish