You’re offline. This is a read only version of the page.
Announcements
275
Hoping someone can please offer thoughts on this behaviour. We've got a pair of Tier 1 cloud-hosted environments in an LCS project with TFS for the extension developments. On the Dev box, the custom models all build successfully, so I've attempted to check a series of changes. The gated checkin pipeline then fails with 11 errors, all thrown by objects that have been deleted within the changeset. The pipeline shows the deletes in its Checkout task, so I can't understand why the build is then attempting to compile the objects.
Example error:
C:\DynamicsSDK\Metadata\Microsoft.Dynamics.AX.Application.Build.targets(40,5): error : Error: AxMap/CUSLetterTemplateMap/Mappings/CUSLetterTemplate/Connections/LegalEntity/MapFieldTo - Field 'LegalEntity' does not exist. [C:\DynamicsSDK\Metadata\BuildMetadata.proj]
Checkout task extract:
Metadata\CUSDevelopment\CUSDevelopment\AxMap:
Unshelving delete: CUSLetterTemplateMap.xml
I've tried a remote desktop connection onto the build machine whilst the pipeline is running, monitoring the metadata folder above, and I can see the relevant map appearing in the folder, being deleted, and then appearing again as the error gets thrown.
Any thoughts gratefully received.
It's strange that the map exists on the build VM. The build shouldn't have to delete it. Because the build environment shouldn't contain any custom code (when it's restored from the clean backup at the beginning of the build), and the map doesn't exist in source control anymore, it simply shouldn't be downloaded when the workspace is created.
I suspect that the backup actually isn't clean - it already contains your objects.
[/quote]Thanks Martin: you're right about the backup (meaning the J\:DynamicsBackup\Packages folder) containing the custom models & ISV models that make up the deployable package I'm expecting the pipeline to build. I haven't found any documentation on this folder, but I see two prior threads (Package build process creates new files, Error on prepare for build) that give a decent explanation of its purpose & origins. Slightly frustrated I didn't find either of those threads before posting & have led you to repeat what others have suggested to resolve similar issues. Having removed the custom model folders from the backup packages folder, the build is now working, so hopefully I'll remember that one (though I also hope not to see the backup in an unclean state again!)
It's strange that the map exists on the build VM. The build shouldn't have to delete it. Because the build environment shouldn't contain any custom code (when it's restored from the clean backup at the beginning of the build), and the map doesn't exist in source control anymore, it simply shouldn't be downloaded when the workspace is created.
I suspect that the backup actually isn't clean - it already contains your objects.
#1
André Arnaud de Cal...
294,095
Super User 2025 Season 1
#2
Martin Dráb
232,866
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
