So you got a bacpac file from a Tier2 environment, and want to import into a Tier1 - but it fails, because of new SQL Server features / instructions / objects / etc.
Not a problem!
Use #d365fotools and get on with your work!
Repair-D365BacpacModelFile comes with default things it will remove, but it actually supports adding your own rules - to fix the bacpac(model) file - instead of doing a new export from LCS.
#MSDyn365FO
Ready - set - go!
There is a new PowerShell module in town. It sits right in the middle of D365FO & Dataverse.
With things moving away from LCS, into PPAC and with the One Dynamics One Platform focus from Microsoft, we felt the need to have more tools available to assist with some of the tasks.
The tools is an administrator tool, but can be utilized by developers and technical people alike.
In its current form, it might feel a bit rough on the edges, but things will evolve over the coming months, when we implement more capabilities.
#D365FO #Dataverse #d365baptools
@wojzeh It's not from 37, it's from earlier version, just stumbled across it when reviewing failed batch jobs and was like why there is usmf in the error and then looked at the code 😐
@wojzeh That it gets called by DirReleaseUpdateScriptController after a version upgrade and batch job fails with "Stack trace: The company usmf does not exist."... And why do I need this in my Prod environment ?
@sohaibcheema@LaneSwenka That's a really bad way to communicate, have so many confused customers who are not on 36 scared that it will update them to 36.