New resources available on Microsoft Learn
Did you know that Microsoft Learn offers free training modules to assist you on your path to mastering Dynamics 365 for Finance and Operations? Become an expert at your own pace or share with your team to foster growth.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
We are happy to announce our first release of an Azure DevOps task in the Visual Studio Marketplace to support Dynamics 365 for Finance and Operations ALM processes. We have more tasks and features planned, and we will continue to publish updates and features as well as new tasks as they become available.
This first release contains a single task that can be used in a Release pipeline to upload your software deployable package to a project's asset library in Dynamics Lifecycle Services (LCS). As this task is being released, the team is hard at work to create the next task which will allow customers and partners to deploy a specific asset from the asset library into their environment, which will complete a set of two tasks to allow continuous deployment for X++ developers!
We realize documentation is needed so we are also working on adding detailed documentation for these tasks on our docs website. For those who can't wait, the only detail that may not be intuitive and requires some specifics is the need for an application registration in Azure Active Directory for your Azure DevOps to connect to LCS. For the tenant used for the LCS project in question, you need to register a native application in Azure AD and give "Dynamics Lifecycle services" API permission as per this documentation (we recommend using the new preview app registration feature). Ensure the user you will use for the connection has access to the project, as well as granted consent for the application registration in Azure AD. Review the consent documentation to enable a specific user, or grant admin consent for the whole tenant.
Also note that the release task can execute on a hosted agent and doesn't require a build VM or otherwise private agent. When using hosted agents, make sure to use the latest host ("Host VS2017").
@The Deployer, i am getting the "Leaf path not found" error even when the release pipeline is configured with the following Dynamic path : $(System.DefaultWorkingDirectory)/_Build AWMS - Development/Packages/AXDeployableRuntime_7.0.5286.41360_$(Build.BuildNumber).zip. The root issue here is the Dynamics version so the release works until the environment its updated/upgraded. Is there a way that we can go around the Dynamics' version number in the package name (in my case: 7.0.5286.41360)? is there a token/wildcard that can be used to get the latest package generated?
It seems that over the weekend the Preview Mode became GA (I was in 'legacy' version fine last week).
You can however still access the old version within the App Registration screen - 'Still want to use App registrations (Legacy)? Go back and tell us why' just above the list of applications.
You have to do this as the app has to be a true legacy version Native app - the replacement, 'Public client Mobile & Desktop' is completely different, but is the only option other than Web in the new App Registration. Worked straight away when created this way for us having already done the other config as per the instructions.
Oh and this is AMAZING. Thankyou!!!
@Kasthu: Looks like you have an issue with the AAD setup. Make sure the client app ID is created as "native".
@steen.rabol/Dick Wenning: you should tie your release pipeline to your build. Picking up the package from a folder from a previously run build is not a good idea. See docs.microsoft.com/.../artifacts .
I'm facing the same issue as Dick Wenning, any suggestions ?
Business Applications communities