I have the problem in call center in D365 that the unit price that corresponds with the sales unit change isn't saved to the DB. This is a Microsoft bug and they are looking into it.
However before we finally contacted them we tried to look for a hotfix. We found KB4134678 which in reality is one enormous group of KBs on the binary and application side. I have put it in place but it didn't solve the problem , looked like it made it worse.
Now I need to get the changesets out of there.
The reason why is because we do not have the time or manpower to do such an intensive testing because of the enormous amount of change that goes in. I also have to go through my custom to make sure it is still compatible. If it worked and fixed our issue with call center, it would be a no brainer to go through the effort, but it doesn't work and cannot take the chance that it introduce even more issues.
With the hotfix I first had to check in the "prepare" set of code that created a changeset. Apparently this is if you need to roll back. It sets all of the entries to "add". Then one applies the hotfix and it creates another changeset. The latter either change the action to an edit or keep it as an add.
To get the changeset out, I then rolled back the "apply" changeset. But for all the entries that the apply action put in as "add", it went and deleted it. So, although ApplicationSuite had "Tax Engine Application Suite Integration" in its descriptor file, it still put it in the changeset as "add" and thus on the rollback, it went and delete this file out of the descriptor. The directory is still there under ApplicationSuite but it is no longer in the descriptor to mark it as a dependent package for ApplicationSuite. So now I have a 1000 errors created by model build. Also, class TaxEngineInventMovement was deleted that is an existing class used in InventMovement.
So the rollback made a big mess. All those changesets are in my TFS because I had to check it in. I tried to rollback the rollback but got access denied errors.
I know in AX2012, when we set up TFS we did it wrong for the reports and a consultant we worked with disconnected TFS in the AOT and then set it up again to pull from the AOT to recreate it.
How can I do that in D365 with Visual Studio linked to TFS and not the AOT linked to TFS? If I can't , how can I delete the unwanted changesets? Luckily I have 2 development environments, but I cannot do a get latest and when I do a merge between Dev and Main at this point I have to work around the changesets that I cannot afford to go into a build and mess up another environment and delete files that shouldn't be deleted.
I need TFS to be in sync again with my environment that at least still work that I luckily haven't installed the hotfix on.
Any options that worked in your environment and that you are willing to share, will be much appreciated.