Hi Gwen,

If you rollback your code then after doing enhancement in DEV and deploy to QAS then data will be loss from ChangeRequestDetail entity.

Regards

Shashi Kant Shukla

Rolling back and redeploying different versions of your OutSystems application can be risky, particularly if it involves changes to the database schema. Here are some key considerations and potential risks:

Risks and Impact

1. Data Loss: If you rollback to a version where the ChangeRequestDetail entity does not exist, any data stored in that entity will be lost unless you backup and restore it appropriately.
2. Schema Mismatches: Rolling back and redeploying can cause schema mismatches between DEV and QAS environments, potentially leading to application errors.
3. Deployment Conflicts: If changes made in the rolled-back version conflict with those in the current version, it can cause issues when attempting to merge or redeploy changes.
4. Business Disruptions: Since the business users are performing UAT in QAS, rolling back and redeploying can disrupt their testing and affect the continuity of their work.
5. Version Control Issues: Managing multiple versions and ensuring that the correct version is deployed to the right environment can be complex and error-prone.

Thanks @Shashi Kant Shukla & @Manikandan Sambasivam for the advised and explanation!

I'm more concern on the deployment conflict or database upgrade error which could have the possibility to mess up the application.

Btw, it's great to learn from both of you and the key consideration listed down is very helpful. :D

Cheers,
Gwen.

Hi Gwen

if you rollback to a version where ChangeRequestDetail  is not there, then in DB the table will still exist with its data.

if you publish a new version with ChangeRequestDetail then a new table will be create in DB. Generally the name of table is appended with number eg- 1,2.....

There will not be any issue in deployment or database error.