We have a situation where several objects that were checked-in to Team Foundation Server are causing issues in Dev environments when those Dev environments are Synchronized (AX 2012 R2). This was due to our AX partner having to change & check-in those objects as part of a hotfix installation in one of our Dev environments; other Dev environments now have Build and CIL compile errors after Synchronizing because those changed objects are causing issues.
The changeset containing these objects has not yet been merged via Visual Studio into the Main branch, so it has not been processed in the AxBuild. So we are able to prevent the changeset from going into PRD as long as we remember to not select it in Visual Studio when merging changesets into the Main branch.
So my question is... without deleting the changeset or restoring the objects in the changeset back to their previous versions, how can we exclude this specific changeset when Synchronizing our Dev environments?
------------------------------
Rudy Salcedo
Senior Programmer/Analyst
LaForce, Inc
Green Bay WI
------------------------------