Updated your BuildVM, but have you checked this with your pipeline?



Once we have successfully updated your Build VM with a quality update or service update, we also need to update the 'Add licenses to your deployable package' step, if your pipeline does have this step:


For this, you need to visit your LCS and check the version of the VM instance:


Copy the build version, and paste it in the 'Add licenses to your deployable package' step:


And update it in the highlighted step.

That's it. If you don't perform this, the Build, Sync and the rest of the steps of the pipeline process might succeed, but it will fail at the above step.

Comments

Post a Comment

Popular posts from this blog

How to handle the error "Could not grant admin consent. Your organization does not have a subscription (or service principal) for the following API(s): Dynamics ERP" in Azure Portal

Image
  If you are an RnD minded developer, any time in your life you must have faced this situation: You needed to perform some POCs on Azure App registrations in your trial Azure instance. You are using a trial Azure sign up instance, using your credit card. You needed to let your Azure App to grant access to Dynamics ERP. So you went to Azure App registrations --> API permissions and Grant admin consent for default directory: But uh-oh, snap!!! You got this error:  Could not grant admin consent. Your organization does not have a subscription (or service principal) for the following API(s): Dynamics ERP . You googled and found out this happens, when you are not a 'Global administrator'. You checked from Azure Directory users' privileges. Yes, you're already a global admin. Then? What happened? What is causing this error?  The following steps, could help you in resolving the same. Read along. Step 1: visit the following site to set up a Premium P2 trial https://learn.micr...
Read more

Tired of Azure Functions ? Switch to Azure Data Mapper for Logic Apps transforms

Image
  Azure data mapper is a very convincing way of transforming your data schemas, without involving little or no requirement for coding, and a easy to use: a. Drag and drop facilities b. A rich built-in library contaning a good number of assisting functions  c. You can manually test the mapping/preview the data. d. Ability to Debug e. Ability to use them on API Management services and Logic Apps very easily f. An overview pane to review if your mappings are correct. A lot of emphasis have been laid on transforming myriad file types: a. XML to XML b. JSON to JSON c. XML to JSON and vice versa However, yes, there are limitations too. As of now: Data Mapper currently works only in Visual Studio Code running on Windows operating systems . Data Mapper is currently available only in Visual Studio Code, not the Azure portal, and only from within Standard logic app projects, not Consumption logic app projects. Data Mapper currently doesn't support comma-separated values (.csv) files. ...
Read more

Make your menu items visible on main menu, conditionally,, using this cool feature of D365FO

Image
  Wassup guys? I am sure you must have encountered this situation where you needed to display your menuItems, on main menu, based on some condition, haven't you? This was only possible by using config keys and flights. Things get a bit tricky,  when suppose you have a requirement like this: you need to make it dynamic, by introducing a toggle switch on a field on a paremeter form.  Suppose on Accounts Receivables Parameters >> You have a field called ' Show US customer '. You have a requirement that says when you turn on this toggle, then only the menuItem ' Input SSN details ', under AR module. This is now highly acheivable by leveraging subscription to 'SysMenuNavigationObjectFactory' class, simply by saying a. Create a new class USMenuItemsVisibilityManager b. Copy the following method, with proper documentation (don't change signature/anything else) [SubscribesTo(classstr(SysMenuNavigationObjectFactory), staticdelegatestr(SysMenuNavigationObjec...
Read more