Repository navigation
Deleted records being skipped in global application #145
Replies: 3 comments 2 replies
|
I’ve seen this. I normally have an agent do a sweep and remove them via the rest api but it does feel unexpected to me. |
|
Bumping this. The pipeline is pretty much unusable in its current state... If I have to manually go resolve skipped records, or create a hacky script to revert to base on every deploy, it is not really prod ready. |
|
@ChristianHesberg This is the standard flow for deleting records, all deletes are 'opt-in' when installing on a new instance. Your deleted records need to be marked as skipped after install to the test instance. There is a property |
Uh oh!
There was an error while loading. Please reload this page.
I have a custom application in the global scope. When I remove the resources in the code, it correctly marks the resources as deleted when building the application. When I install on my DEV instance, the resources are correctly deleted. I then publish the new application to the Application Repository. When I pull the changes onto my TEST instance, the records are marked as deleted, but they are skipped. I then have to go in and manually revert these records back to the base system.
I also notice that other records in the install are "skipped" but there are no differences between the record on the instance and the skipped record.
Has anybody else experienced this problem? Could this be caused by a misconfiguration?
All reactions