In this blog, we will see how to enable Administration Mode from Power Platform Admin Center. Enabling the Administration Mode comes in handy while performing operational changes to the environment like copying a sandbox instance to the production. Previously, this setting was available from the Office 365 portal for sandbox instances. For more details, you can refer to this blog.

Administration Mode can be enabled for Sandbox, Production, and Trial (Subscription-based) instances. So once enabled, only the users with the security role of System Administrator and System Customizer can access the environment. Enabling the Administration Mode ensures that neither non-administrators nor administrators affect each other’s work.

Let’s see how to configure ‘Administration Mode’:

1. Navigate to Power Platform Admin Center Login with Environment Admin or System Administrator -> Navigate to Environment from the left-side menu.

2. Select the Environment and Click on Open.

3. In Details, select Edit.

4. Enable the Administration Mode.

5. Post enabling the Administration mode, you will get the option to disable or enable the Background Operation. By default, this option is enabled.

If you disable the Background Operation, it will disable all asynchronous operations like workflow, and synchronization with Exchange.

6. Now the Custom Message field is no more editable as it is being removed -> Click on Save.
7. After saving, the environment gets updated.

Once it is completed, you can see a notification on the Environment page stating that ‘This environment is currently in administration mode, so only admins can sign in to it. You can turn off administration mode in settings’.

Now, only users with System Administrator or System Customizer security role can successfully access the environment.

Whereas, other end users i.e. non-admin users will not be able to access the environment.

Conclusion:

In this way, administrators can manage and maintain the environment by setting it in the ‘Administration Mode’ from Power Platform Admin Center.

Please visit the Source and support them

The post Enable Administration Mode from Power Platform Admin Center appeared first on Microsoft Dynamics 365 Blog.

With Power Automate FLOW, we can execute a huge number of operations by connecting various systems. Now, we are talking about the Dynamics 365 CRM where we can execute the Actions of Dynamics 365 CRM. Here, we know that with the “Perform an unbound/bound” action step we can execute the CRM actions. So, we are trying to execute one of the CRM actions that are “WIN/LOSE OPPORTUNITY” but this action is not that simple as compared to other actions.

Here, you can see we have “WinOpportunity” action is available in the “Perform an unbound action” but this action is not working as per our expectation and we are getting below error.

So, to execute the “WIN Opportunity” action, we found an alternate solution. Let’s discuss the same to WIN an opportunity using Power Automate FLOW.

Solution:

To WIN opportunity using Power Automate FLOW, follow the steps given below:

1. Basically, we need to specify the action name inside the “Perform an unbound action”. No need to use its in-build option to select “WIN Opportunity” as we tried above.
2. So, for this you need to store the Action name in one Variable as you can see in the below screenshot:

3. After storing the “WinOpportunity” action name, you need to map this variable to ‘Perform an unbound action” step where your “WinOpportunity” action will be executed.

Note: Here we must store the Action name inside the Variable. We cannot directly write “WinOpportunity” name inside the “Perform an unbound action” step.

4. Map ‘actionName’ variable in Action Name.
5. Set the parameters of the Action like Opportunity ID as shown below:

6. After setting the action parameters, the steps will look as below:

7. With this above step, we can execute the WinOpportunity action easily.

Similarly, we can execute the Lose Opportunity as shown below:

In “Status” you can pass the 4 (Canceled) or 5 (Out-Sold) according to your requirement.

So using this you can close the opportunity as Lost.

Conclusion:

In this way, by using Power Automate FLOW we can WIN/LOSE Opportunity in Dynamics 365 CRM/CE.

Please Follow the Source

The post How to WIN/LOSE Dynamics 365 CRM Opportunity through Power Automate FLOW appeared first on Microsoft Dynamics 365 Blog.

Power Automate has released many new things one of which is Process Advisor which instantly collects precise stages for each process in your company, allowing you to better identify where workflows could be optimized. Some more benefits of Process Advisors are as follows,

• Determine which tasks take the most time
• Find out which activities are the most popular
• Understand where the bottlenecks are

What’s New?

So recently, Power Automate introduced Automation Recommendation in Process Advisors.

The automation recommendation feature in process advisor assists you in identifying automation opportunities. It also walks you through the process of automating your processes with Microsoft Power Automate.

In short, it recommends connectors and action for the step in your Power Automate Flow based on the recordings that you add in it.

Pre-requisites – Power Automate Desktop

How does it work?

To make it work, you need to create a Process Advisor and add some recordings in it, from which it analyses and recommends the steps to you in the Power Automate Flow.

So let us start by creating a Process Advisor in Power Automate.

After creating the Process Advisor, we will need to add some recordings of our actions in it. You can add multiple recordings in it. The recordings are a way to train the Process Advisor to recommend us with the connectors and actions while creating the Power Automate Flow.

For example, we will add two recordings to send an email from Outlook and Update an online excel sheet in Process Advisor.

You will get an alert as shown below.  Now, open the Power Automate Desktop.

Click on ‘Record’ to record your actions and ‘Finish’ after you are done with the recording.

We will now add two recordings – one for the mail in outlook and one for the Excel sheet.

Below are the actions in the outlook mail recording. Now we need to divide these actions into at least two activities/groups for the Process Advisor to analyse them.

After grouping of the actions and creating activities turn on the Ready to analyze button.

Last thing is to analyze the recordings by clicking on the Analyze button. With this, our two recordings will get analyzed.

Note: The Process Advisor analyzes only the recordings with “Ready to Analyze” as “Yes”.

After analysing the recordings, the status of the recordings will change to Analyzed as shown in the image below. Now click on the Analytics button that appears only after the Analysis of at least one recording is done. It will redirect us to the process maps and legend.

The process map as shown below, allows you to see and evaluate processes. You may gain insights into where possibilities exist by looking at a graphical representation of how your business operations are executed.

Activities are now the tasks or actions that comprise a business process. Activities can be done by humans or, in the case of automation, by machines. Different activities are represented as nodes in the process map, while transitions between activities are represented as edges. Each process sequence will have a start and an end.

The blue circle icon represents that the Process Advisor will recommend connectors/actions on that particular step in the flow as shown above.

You can further see the descriptions of respective components in the Legend section.

Now to see those recommendations, click on Automate activities on the top.

The below page will be opened, where you can create your Power Automate Flow.

The Process Advisor goes through all of your activities or groupings of actions and recommends connectors and actions. These suggestions can be found in the Automate activities section.

You can also share your Process Advisor with your teammates so that they can add their recordings, which will be considered for showing the recommendation.

How can it be used?

These recommendations can be very useful for a team, which has multiple approaches for a process to work.

By reading the process map, you can calculate the time and come up with the best suitable approach to make your process work even more efficiently.

In other words, it helps users achieve the same results with the help of diverse recommendations in addition to which it also enables the automation ability on various milestones (example: handling Email, OneDrive, Excel) while designing the process flow.

Conclusion:

As illustrated above, you can easily explore the possibilities and applications of Automation Recommendation of Process Advisor and improve your efficiency.

Please Follow the Source

The post Exploring Automation Recommendation in Power Automate Process Advisor appeared first on Microsoft Dynamics 365 Blog.

As seen in our previous blog, we can create a custom API that can be triggered in Dynamics 365 CRM Workflows. But since Microsoft is moving away from Dynamics 365 CRM Workflows to Power Automate Flows, we should too. So, in this blog, we will see how to use the same Custom API in a Power Automate Flow.

After creating a custom API, follow the steps given below:

1. Navigate to your environment from powerapps.com and to your solution -> Click on New -> Select Cloud Flow.

2. Search for “when a row is added” in the trigger and select “When a row is added, modified or deleted” trigger.

3. Rename the flow step. (Note – It is recommended to uniquely name every step to prevent confusion in case the power automate flow gets a bit complex).
   1. Select ‘Added’ in change type and ‘Accounts’ in Table Name since we want this flow to run when a new account is created.
   2. Choose scope from Organization/Business Unit/Parent: Child Business Unit/User as per your requirement.

4. Click on New Step -> Search for “Perform a bound action” and Select “Perform a bound action” from Actions.

5. Rename this flow step.
   1. Select ‘Accounts’ in Table name since our custom API is bound to the Accounts entity.
   2. Select the action by its unique name in Action Name.
   3. Select unique identifier of the Account (added in the previous step) in Row ID as shown below:

After this, the step would look like below.

6. This is pretty much it. Next, give a proper name to your flow and save it.

7. Now, whenever an account record gets created, a phone call activity associated to the account will also get created with the due date set as the next day and thus can be seen in the Timeline as well.

Conclusion: In this way, we can easily use the custom API in Power Automate Flow.

Please Follow the Source

The post Use of Custom API in Power Automate Flow appeared first on Microsoft Dynamics 365 Blog.

Most of you would be well acquainted with our popular assignment automation app for Dynamics 365 CRM – Lead Assignment and Distribution Automation. Already a Preferred app on Microsoft AppSource, Lead Assignment and Distribution Automation is a productivity app that automates the allocation or distribution of Leads (or any other entity records) recorded in Dynamics 365 CRM. In this way, it ensures that Leads are not mismanaged or overlooked and are assigned to users automatically thereby improving the chances of creating new customers and increasing sales.

Now, let’s reiterate why Lead Assignment and Distribution Automation is the apt app for assigning Leads, Cases or any other entity records in Dynamics 365 CRM.

Say Goodbye to Manual Assignment of Leads

With this assignment automation app, you can assign Leads (or other entity records) to your team members using Round Robin or Capacity Algorithm. With Round Robin algorithm, the incoming Leads will be evenly distributed among your team members. If there are three members in your team and there are six incoming Leads then each member will be allotted two Leads.

But with Capacity Algorithm, the individual capacity of each team member will be taken into consideration. Here, you will be given the provision to determine the capacity of each team member depending upon their experience. And based on this capacity Leads will be allocated to your team members. Here, the most experienced team member will be assigned more Leads as compared to the least experienced team member.

Assign Leads in Sequence

With this feature of Lead Assignment and Distribution Automation, you can set a sequence or order to distribute the Leads to your team members. This will work for both Round Robin and Capacity algorithm and the Leads will be assigned from lowest to the highest sequence. So based on performance, experience or any other factors you can decide to set a sequence and determine who will be the first to get the share of incoming Leads.

Partnership in Leads

With Lead Assignment and Distribution Automation app, you can automate the process of transferring Leads from one team member to another by using workflows (Classic & Power Automate Flows) in Dynamics 365 CRM. There may be cases, where it may seem prudent to first assign Leads to one team member for initial footwork and then assign it to another team member for sales conversion. This will build partnership between team members and enhance productivity.

Now, all of these processes which used to be done manually can be automated with this amazing app. You have to just do three things – Get it, set it and forget it. In other words – get Lead Assignment and Distribution Automation app set it as per your requirements and then forget about it.

Sounds tempting, isn’t it?

Then go to our website or Microsoft AppSource to download this amazing assignment app for a free trial of 15 days and experience how automation of Lead assignment can boost your overall productivity.

And feel free to share your experience and expectations at crm@inogic.com

While we have been talking about Leads how can email marketing be left behind – it’s time to also look at our latest integration app – Marketing4Dynamics which integrates Mailchimp (one of the most famous and used email marketing software across the globe) with Dynamics 365 CRM.

Until then – Stay Healthy, Stay Wealthy!

Please visit the Source and support them

The post 3 Best Practices for Increasing your Lead Conversion Rates – Lead Assignment and Distribution Automation in Dynamics 365 CRM is what you need! appeared first on Microsoft Dynamics 365 Blog.

With the new updates of PowerApps Component Framework, now we can develop the PCF control for lookup field. Earlier, there was no supported way to develop the PCF Control for lookup field. However, with the new update, we can do this by using the lookup type property. In the below example, we have created a PCF control for lookup field and added the same on ‘Primary Contact’ lookup field of Account entity.

Given below are the steps to achieve the same:

1.     First, we need to add lookup type property in ControlManifest.Input.xml file using the code given below:

<property name=”sampleProperty” display-name-key=”Property_Display_Key” description-key=”Property_Desc_Key” of-type=”Lookup.Simple” usage=”bound” required=”true” />

2.    Next, define the ‘IInput and IOutputs’ for lookup in d.ts file.

// Define IInputs and IOutputs Type. They should match with ControlManifest.

export interface IInputs {

sampleProperty: ComponentFramework.PropertyTypes.LookupProperty;

}

export interface IOutputs {

sampleProperty?: ComponentFramework.LookupValue[];

}

3.     Now, add the action that on click of ‘Find Lookup’ button, it opens the lookupObjects to select the value:

private performLookupObjects(entityType: string, viewId: string, setSelected: (value: ComponentFramework.LookupValue, update?: boolean) => void): void {

// Used cached values from lookup parameter to set options for lookupObjects API

const lookupOptions = {

defaultEntityType: entityType,

defaultViewId: viewId,

allowMultiSelect: false,

entityTypes: [entityType],

viewIds: [viewId]

};

this._context.utils.lookupObjects(lookupOptions).then((success) => {

if (success && success.length > 0) {

// Cache the necessary information for the newly selected entity lookup

const selectedReference = success[0];

const selectedLookupValue: ComponentFramework.LookupValue = {

`              id: selectedReference.id,

name: selectedReference.name,

entityType: selectedReference.entityType

};

// Update the primary or secondary lookup property

setSelected(selectedLookupValue);

// Trigger a control update

this._notifyOutputChanged();

} else {

setSelected({} as ComponentFramework.LookupValue);

}

}, (error) => {

console.log(error);

});

}

4.      Next, on load of Lookup PCF control, set the current value in lookup using UpdateView function.

public updateView(context: ComponentFramework.Context<IInputs>): void

{

// Add code to update control view

//Update the main text field of the control to contain the raw data of the entity selected via lookup

const lookupValue: ComponentFramework.LookupValue = context.parameters.sampleProperty.raw[0];

this._context = context;

let propertyValue:any = lookupValue.name;

this._input.value = propertyValue;

}

5.      Finally, set the changed value of lookup using getOutputs function.

public getOutputs(): IOutputs

{

// Send the updated selected lookup item back to the ComponentFramework, based on the currently selected item

return { sampleProperty: [this._selectedItem] } ;

}

Conclusion:

In this way, with the help of new lookup type property, we can easily create PCF control for the lookup field.

Go to Source and hit them a thumps up

The post How to create simple Lookup using PCF Control appeared first on Microsoft Dynamics 365 Blog.

We are already aware of the Advanced Lookup feature that Microsoft has added in the Release 2021 Wave 1. And along with it some additional features have been introduced to trigger a typeahead search in Advanced Lookup behavior i.e., “Minimum number of characters to trigger typeahead search” and “Delay between character inputs that will trigger a search”

Now, let’s see how it works!

In the Power Platform Admin Center, go to Settings > Behavior and look under Lookup Behavior settings.

Using the “Minimum number of characters to trigger typeahead search” field, you can trigger a typeahead search in the Search box present in the Advanced Lookup window based on the number of characters you enter.

For example: If you set 0 in the field, then typeahead search will get triggered immediately after each character you enter in the search box. But if you set the limit to trigger your typeahead search i.e., minimum of 5 characters in the field then the typeahead search will get triggered only after you enter the 5^th character in the search box.

As you see below, I have entered only 4 characters and the typeahead search has not been triggered.

And once you enter the 5^th character, you will see the typeahead search has been triggered and showing the expected result. In addition to the same, the “Delay between character inputs that will trigger a search” field is used to trigger a typeahead search based on delay occurred while entering the input characters in the Search box present in the Advanced Lookup window.

For Example: If you set 30000ms in the field and if “Minimum number of characters to trigger typeahead search” field value is set to 5 then after entering the minimum character i.e., 5, if you do not enter any character or enter the next character with the delay of more than 30000ms then typeahead search will get automatically triggered and will show the result.

As you see below, I have entered 6 characters in the search box but without any delay between characters so the typeahead search has not been triggered yet.

And now if you don’t enter any character or enter the next character with the delay of more than 30000ms then you will observe the typeahead search has been triggered after 30000ms howing the expected result.

Note: You can enter the value in the “Delay between character inputs that will trigger a search” field between predefined range only i.e., Minimum Value: 250, Maximum value: 2147483647, or else the below message will be displayed after youSave it.

Conclusion:

In this way, with the above features you can easily control the typeahead search trigger in Advanced Lookup.

Reference: https://docs.microsoft.com/en-us/powerapps/user/lookup-field#advanced-lookup

Please Follow the Source

The post Controlling Typeahead Search Trigger in the Advanced Lookup appeared first on Microsoft Dynamics 365 Blog.

In the recent release, Microsoft added one powerful feature called ‘Global Intelligent Search’. In this blog, we will see how the admin can enable this for the organization and how it helps the user, and some tricks to get quick results.

Enable Relevance Search:

1. In the Power Platform admin center, select an environment.
2. Select Settings> Product > Features.
3. Under Search, set Relevance Search to On.
4. Select Save.

Note: Once you enable this option it will take 5-10 min.

Click Here to Know more about relevant search configuration.

Once Admin is done with enabling and configuring the option then within CRM a search option will be available on the top.

Now we will show you some tricks so that you can easily find records quickly using binary operations.

1. Here, first I entered ‘Contoso’ and saw that it is showing all the records with the word Contoso.

2. Next, I entered the Account name + primary contact name as ‘Contoso + Calvin’ and it displayed only those records whose account name starts with Contoso and primary contact is Calvin. So, by using ‘+’ button you will get an exact match.

3. But now, I’m looking for a record where the account name contains Contoso or contact person is Calvin. In this situation, I’ll use ‘Account name | primary contact name’ format i.e., ‘Contoso | Calvin’. Now it displayed all the records whose account name starts with Contoso and primary contact is Calvin. Here by using ‘|’ button, I will get all the records whose account name is Contoso or primary contact is Calvin.

4. Similarly, now I want all accounts to start with Contoso but primary contact should not start with Calvin. For this, I will search by using Account name + (-Primary contact name). So I will enter ‘Contoso –Calvin’ in the search option and it will get all account records except the primary name starting with Calvin.

5. Sometimes it happens that you don’t know exact spelling or you just know the start or end word of any field. In this case, you can use ‘*’ before or after any word so it will give all the records as per the asterisk mark. In the below case, I entered ‘Con*’ so it will get all records starting with Con.

6. If you are looking for an exact match then just enter the word in the double quotation so it gets only those records which are exactly matched.

Also, when we search for any records then we mostly perform some common actions. These are now by default available within the search result called as ‘Quick Actions’. So, now you don’t need to open the records to perform an action. You can simply search for the records and perform actions as the actions are available there itself as shown below.

In the next blog, we will see how Quick Actions can be configured.

Please visit the Source and support them

The post How to get quick results by using ‘Global Intelligent Search’ appeared first on Microsoft Dynamics 365 Blog.

We recently had a business requirement to load data in Dynamics 365 CRM. We had a case where the user will create Account records in a CRM and at the end of the day, it should load records in the other Dynamics 365 CRM. To achieve this we have used the Azure Copy Data Activity tool, also we have configured scheduling on the “Copy Data” tool so it will Upsert records in the target system once a day.

In this blog, we have explained how we have configured the ‘Azure Copy Data Activity’ tool to Load records. So, let’s have a look at the steps we followed to achieve the same.

Step 1: Connect to the Azure https://portal.azure.com and navigate to the Data factory. If you don’t have a Data factory then create it first to use the ‘Copy Data Activity tool’.  Please refer to the below link to know how to create a Data factory:

https://docs.microsoft.com/en-us/azure/data-factory/quickstart-create-data-factory-portal#create-a-data-factory

Step 2:  We already have a Data factory i.e. “DataLoadActivity”, so we are using that but to add the Copy Data Activity tool, you need to add a pipeline.

DataloadActivity (Data factory) -> Author & Monitor -> Author -> Create new/Existing Pipeline -> Drag and Drop Copy Data.

Please refer to the below screenshots:

Navigate to Author & Monitor

Navigate to Author

Add Pipeline

Drag and Drop ‘Copy Data’ tool.

We can change its name from the ‘General tab’, we have renamed it as ‘Load Accounts’.

Step 3: In the next step, we need to add a new dataset and configure a connection with Dynamics 365 CRM. To configure the dataset, we need to click on the Dataset menu and add New Dataset as shown below:

It will open the Data Stores window. Here we need to select Dataverse (Common data service for app) and click on continue.

Once the dataset is added, we need to add link services. To add link services, click on the +New button and it will open another window where we need to set CRM connection details.

Here, we need to pass details i.e., Name, Service Url, Authentication type(AAD Service Principal), Service Principal Id(Azure Active directory App Id) and service principal key(secret key) details. And after the ‘Test connection’, click on Create.

• Name: Connection name
• Connect via integration runtime: AutoResolveintegrationruntime
• Deployment Type: It has two options i.e. Online and OnpremisewithIfd. As we are connecting to Dynamics 365 CRM online, so need to select online.
• Service uri: Dynamics 365 CRM url
• Authentication Type: It has 2 options i.e. AAD service Principal and office365. Need to select ‘AAD service Principal’ option. FYI, office365 is deprecated now.
• Service Principal credential type: Select ‘service principal key’ and then it will ask to enter Azure Active directory App Id and secret key.
• Service Principal ID: Need to pass Azure Active Directory Application(client) Id.
• Service Principal Key: Need to pass Azure Active Directory Secret key.

To establish a connection, you must have Azure Active Directory and use the App Id and secret key from the Azure Active Directory app. You can refer to the below article to know about how to configure/create Azure Active Directory app:

https://www.inogic.com/blog/create-azure-active-directory-app

Once Azure Active Directory app is configured, you need to create an Application user in CRM. To configure the Application user, we need to pass Azure Active Directory Application ID (App Id) as shown below:

After this, we need to select the table name under connection. As we want to load data for the Account table so here we select the Account table. Using the same way, we have set up a dataset/connection for both Source and Target CRMs.

Step 4: Now, we can set up the “Copy Data” tool. In the first step, we need to set up a Source detail, as shown below. Here, we have selected a table but as per the requirement, we can also select Query and pass the fetchxml query.

Step 5: Next, we need to set up Sink details. Here we have selected Target CRM and selected behavior as Upsert. Also, it has other properties i.e. to ignore null values, perform upsert based on Alternate key, etc.

Note: If you don’t want to upsert the record based on the Primary key field (i.e., accountid) then you can use the Alternate key property. You need to set an alternate key in your target CRM table field and then the alternate key will display here under the Alternate key name list.

Please refer to the below article to know how we can configure alternate key in CRM:

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/define-alternate-keys-reference-records?view=op-9-1#define-alternate-keys

Step 6: Once Sink details are configured, we need to set field mapping as shown below:

Note: If you don’t see mapping fields, please click on Import Schemas.

Step 7: We can also add a trigger and configure scheduling to trigger the ‘Copy Data’ tool.

It has multiple options to set trigger i.e., minutes/hourly/day/week. As per our requirement, we have set it to Day(s), as shown in the below screenshot

Step 8: Publish all.

We can also monitor the run history. To check the run history please navigate to Monitor -> Pipeline run.

Also, we can run the pipeline by clicking on Debug without setting any Trigger, please refer to the below screenshot:

Note: I couldn’t get the option/behaviour to perform only Update operation instead of using Upsert.

Conclusion:

As illustrated above, with the help of Azure Copy Data Activity tool, we can load data in Dynamics 365 CRM.

Reference link: https://docs.microsoft.com/en-us/azure/data-factory/quickstart-create-data-factory-copy-data-tool#start-the-copy-data-tool

Source

The post Load Data in Dynamics 365 CRM using Azure Copy Data Activity tool appeared first on Microsoft Dynamics 365 Blog.

Powered by passion – Inogic is a leading Microsoft ISV for Dynamics 365 CRM for over more than a decade. We brew innovative products and fuel Dynamics 365 with our range of solutions. Inogic also offers bespoke high-quality low-cost offshore development services for Microsoft products such as Power BI, Flow, PowerApps, Portals and others.

Given our super modern slick technology, we believe in sharing tips and tricks with our community from time to time. Therefore, we come up with informative blogs and are quite active on community forums. In this blog we are going to compile the top five blogs of 2018 which have been most clicked. Compiling them again for our friends who missed these posts. Thank you so much for sharing our posts and encouraging us to explore Dynamics 365 and Power Platform.

Dynamics 365 v9.0: Xrm.WebApi – CRUD Operations Part – 1

This blog talks about how Xrm.WebApi acts as a boon for developers. In the versions prior to v9.0 one had to create their own libraries or use third party libraries or create XmlHttpRequest and AJAX request. With Xrm.WebApi enhancement in Dynamics 365 CRM v9.0 developers’ life is made easy. In a continuation to this blog Dynamics 365 v9.0: Xrm.WebApi – Operations Part – 2 we have discussed how to Retrieve Multiple records and Execute Actions.

Integrating Dynamics 365 with Azure Functions – Part 1, Part 2, and Part 3

Azure function is a server-less architecture where you can host your code on cloud without any infrastructure. In this blog we have taken example of creating Azure function and called same through workflows. We have also depicted how a function can be executed as an HTTP request. This series of blogs talks about invoking Azure functions from Dynamics 365.

Working on Lookup Field of Dynamics 365 in PowerApps

PowerApps allows building business Apps that run cross platform. Citizen developers with minimal development capabilities can build Apps and deploy them for usability. These apps are modular in nature and these can be dragged and dropped to build an App in short span of time. It allows anyone in an organization unlock new business agility.

Given a business requirement we needed to set lookup fields using PowerApps in Dynamics CRM. This is not inherently supported in PowerApps so after a little research we found out the solution to this. This blog explains the steps to read and set Lookup fields of Dynamics 365 in Power Apps.

Show Lookup Dialog in Dynamics 365 v9.0

This blog discusses about how using the new feature introduced in Microsoft Dynamics 365 v9.0 users can show lookup dialog using Xrm.Utility.lookupObjects method. The parameters required for Xrm.Utility.lookupObjects are list of the entities to be displayed, default entity to be shown in lookup window, Guid of default view, specification whether to allow user to select multiple records and list of views that need to be available for lookup dialog. Using these parameters a lookup dialog can be seen.

JavaScript: “Execution Context” provides Form Values on Web as well as UCI in Dynamics 365 v9.0

After the introduction of UCI there is a generic interface for the end users, this is about UI but behind the scene for developers Microsoft provided “Execution Context” object which is a collection of array. This blog talks about how we can pass the Execution Context using “Primary Control” CRM Parameter to Script function which we can call on Click of Custom Button.

If you want to explore more informative blogs visit this space.

We provide services for PowerApps, Microsoft Flow, Microsoft Portal, Power BI and others. Contact us for any query, suggestion or feedback at crm@inogic.com

Keep Exploring!

Please visit the Source and support them

The post Azure Functions, Web API, PowerApps and other tricks for Dynamics 365 CRM – Most Clicked Blogs of the Year! appeared first on Microsoft Dynamics 365 Blog.