Dynamics 365 for finance and operations tech topics

When upgrading LCS environment we sometimes encounter the error GlobalUpdate script for service model: RetailServer .  Paul Heistkamp wrote a blog post on how to solve the issue here  .  The steps are:  1. Connect to the intended environment. 2. Find the latest deployable package applied to the environment. It will be under folder <ServiceVolume>:\DeployablePackages\ 3. Under the deployable package folder, find the following SQL script <ServiceVolume>:\DeployablePackages\RetailServer\Scripts\DropAllRetialChannelDbObjects.sql This script, when run against the AOS database, will remove all objects related to the Retail Channel Database. Only proceed if you are not using the Retail Channel functionality. 4. Connect to the AxDB database and run the above script. This operation will take several minutes. 5. Resume the package deployment or start the package deployment to have the Retail Channel components recreated correctly. If the steps above don't resolve the problem it m

When pushing a branch that was created locally that doesn't exist in your remote as a user you'll be prompted with the statement suggesting what command to run to create the new branch in the remote: " git push — set-upstream origin <branch-name> " If you are tired of doing a copy paste of the command and running it. Use the git setting push.autoSetupRemote to change the default behaviour in git to automatically create the branch.  Run the git command below to change the global setting.  git config --global --add --bool push.autoSetupRemote true

A great easy tool in market place to mirror a git repo change from Azure DevOps to github repo.  https://marketplace.visualstudio.com/items?itemName=swellaby.mirror-git-repository Just create a pipeline with trigger on the main branch for example and run the task to clone the changes. 

With the launch of the Unified developer experience, it's the perfect time to consider switching to git for source control as it will developers to work on their local computer, branching, switching between tasks and pushing the code when ready to share or they have connection again.   Microsoft has now shared documentation on how to work with git and X++ in their  Microsoft Solutions Playbook, Git walkthrough The yml pipeline files to build FinOps can be found here In our team we have ben using git for the last few years successfully without issues together with X++ development. 

Working in the local development experience for FinOps you'll probably come across the scenario where you add a dependency on a ISV model or other for which you only have the binaries.  When I tested this first I added a dependency for my model to a model for which I only had the binaries in my Metadata folder, building my model and selecting deploy to online environment expecting that it would deploy the model I made changes to and the new reference model. This didn't work.  What I found was that I first had to go to the deploy menu, select the binary models that I depended on and deploy them to the online environment. 

If you haven't heard about this yet, we are about to enter a new era in terms of functionality and development for Dynamics 365 for Finance and Operations as the application is now more seemlessly becoming a part of the Dynamics 365 and Power Platform eco system.  The news that every FinOps developer should be excited about is covered in the Power Platform 2023 release wave 2 and is set to GA in October 23.  Together with the exciting tweet from Lane Swenka hope the release of this is close!  We are getting local developement against cloud environments created in Power Platform.  Read more here   Update 2023-09-14 Official documentation released here