D365 Finance & Operations and Dynamics AX Forum

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
------------------------------

Hi Rudy,

You could revert the objects the Partner changed back to their original version, this would fix the build for all the Dev environments.  To continue working with the hotfix the partner was working on, you could commit the hotfix changes to a branch in TFS.  This way, the hotfix changes are isolated on that branch and will only affect a developer on that branch.

For a developer that needs to work with the hotfix branch, the developer's AX environment can be pointed to the specific branch in the Version control parameters screen:


------------------------------
Ariff Damji
Parts Canada Development Co.
Calgary AB
------------------------------

Original Message:
Sent: Aug 30, 2019 11:32 AM
From: Rudy Salcedo
Subject: How to exclude a changeset when Synchronizing Dev environments

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
------------------------------

Thanks @Ariff Damji, I discussed this with my supervisor and we believe your solution will work for us.  Thanks!​​

------------------------------
Rudy Salcedo
Senior Programmer/Analyst
LaForce, Inc
Green Bay WI
------------------------------

Original Message:
Sent: Sep 03, 2019 09:46 AM
From: Ariff Damji
Subject: How to exclude a changeset when Synchronizing Dev environments

Hi Rudy,

You could revert the objects the Partner changed back to their original version, this would fix the build for all the Dev environments.  To continue working with the hotfix the partner was working on, you could commit the hotfix changes to a branch in TFS.  This way, the hotfix changes are isolated on that branch and will only affect a developer on that branch.

For a developer that needs to work with the hotfix branch, the developer's AX environment can be pointed to the specific branch in the Version control parameters screen:

------------------------------
Ariff Damji
Parts Canada Development Co.
Calgary AB

Original Message:
Sent: Aug 30, 2019 11:32 AM
From: Rudy Salcedo
Subject: How to exclude a changeset when Synchronizing Dev environments

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
------------------------------