VBCS project Issues post refresh
Hi Team,
Following the recent refresh of our non-PROD environment, we’ve noticed that the VBCS project previously used for migrating changes to Production is no longer available. However, the VBCS changes in Production is still functioning and reflecting the expected behavior.
Currently, we have additional VBCS changes in UAT phase that need to be reconfigured, but since the non-PROD environment was refreshed, we will need to reconfigure it. Our concern is that if we create a new VBCS project in non-PROD, it will overwrite the already deployed VBCS changes?
Could you please advise:
- Has anyone faced a similar issue after a non-PROD refresh?