Skip to main content

Dynamics 365 Environmental Variable

  

Dynamics 365 Environmental Variable


This is one of the exiting features that I came across, it can simplify designs and architectures in Dynamics 365 CE.

I am sure most of you have created custom entities to hold your configuration key values. and wished there was a better way to handle environmental configurations.

Now we can take advantage of Environmental Variables to accomplish this:

  1. Environmental variables can be moved through solution

  2. They can be used in your Power Automate Flows

  3. In Plugins or JavaScript


I will leave it to your imagination where you can use Environmental Variables based on  your Use Cases.

To simplify things I will show you how to create Environmental Variables and the various Data Type Options available.

Open an existing or a new solution in https://make.powerapps.com/



You have the following Data Types available for you:

  1. Decimal number

  2. {}JSON

  3. Text

  4. Yes/No

  5. Data Source



 In upcoming blogs I will try to give you some examples on how you can consume these environmental variables from Power Automate Flow to Plugins and JavaScript


Happy Codding :)



Labels:

Comments

Post a Comment

Popular posts from this blog

How to use Formatted Values in Power Automate Flow Dynamics 365

  How to use Formatted Values in Power Automate Flow Dynamics 365   If you have been working on Power Automate for Dynamics 365 you might have been wandering how you can access a lookup Formatted Value or Option Set formatted values. You can use the following format to access: body(‘{Action Name}’)?[‘{fieldname} @OData.Community.Display.V1. FormattedValue’] You just have to be mindful in Dynamics 365 lookup field name they do not translate to the proper field name, you might have to and an “_” as a prefix and “_value” as a postfix, I will leave that to you.
Post a Comment
Read more

Azure DevOps Fork Repos between two Organization

  Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organizati...
5 comments
Read more

XMLHttpRequest vs Xrm.WebApi

  XMLHttpRequest vs Xrm.WebApi If you have written JavaScript code for Dynamics 365 you have seen the use of XMLHttpRequest or Xrm.WebApi to make server-side calls. The question is which one is the right one to use? So, let’s analyze the two types of calls. XMLHtttpRequest 1.        Synchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", false ); 2.        Asynchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", true ); So, passing true parameter is going to make asynchronous call while passing it false is going to make a Synchronous call. Xrm.WebApi 1.        Asynchronous a.        There is...
4 comments
Read more