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.

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.

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.

In this AI Builder three-part blog series, first blog was about how to use AI Builder to extract Form document data and second blog highlighted the use of AI Builder Text classification model.

Now in the third and final blog we will see how to build an AI Object Detector using Power Platform.

Object detection refers to the capability of computer and software systems to detect images, locate objects in an image and identify each object. Object detection can be used to expedite or automate business processes in multiple industries.

AI Object detection is a new feature in Power Platform which can be accomplished using AI Builder. AI Builder allows you to add artificial intelligence to your apps even if you have no coding or data science skills.

Let’s see how an AI object detection model is built using AI builder. On the other hand, Object detection App is built using PowerApps and data is transferred from PowerApps to Dynamics 365 CRM using Microsoft Flow in Power Platform.

1. Build Object Detection Model using AI Builder

a. To build a model using AI Builder, sign in to PowerApps and, in the left navigation pane, select AI Builder > Build. Then select the Object Detection model type.

b. Name your model and Create

c. Select object names – Select the object names by selecting an entity from Common Data Service. Here, we have selected a custom entity with name ‘Electronic Item’ and Field ‘Name’. This entity has records with name of electronic items like Monitor, Keyboard, Mobile and Mouse.

d. Add images – Click on ‘+Add Images’ button to upload images of objects that you want to detect and identify. Upload 15+ images of each object.

e. Tag images– Teach the model to identify objects by tagging and labeling them. For each image, draw a rectangle around the object which you want to identify and tag it with correct name. Go through all the images to tag the objects. Once all the images have been tagged, click on Done tagging.

f. Train Model – Click on Next >Train. It will take several minutes to train the model. Use Quick Test to test the model’s accuracy and then Publish the model to consume it in the app.

Once the model is published its status changes to Live from Draft.

2. Build Object Detector App using PowerApps

a. Click on Create app button shown in previous step. You can create a Canvas App or Model-driven App or Portal from blank depending upon your choice. In our example, we are creating a Mobile Canvas App.

b. Insert Object Detector by navigating to Insert > AI Builder > Object detector. Drag the Object detector to your screen and select the existing object detector AI model.

The object detector control looks like below:

c. Insert a Gallery Control with Title and subtitle layout.

Set the properties of Gallery and its Title and SubTitle as follows:-

Gallery Items  = ObjectDetector1.VisionObjects

Title Text = ThisItem.displayName

Subtitle Text = ThisItem.count

d. Insert some label controls for storing the values of Count for each individual item i.e. Monitor, Keyboard, Mobile and Mouse Counts and set their text properties.

For Example: –

lblKeyboard.Text =First(ObjectDetector1.VisionObjects).count

lblMobile.Text= First(Filter(ObjectDetector1.VisionObjects,StartsWith(displayName,”Mobile”))).count

lblMonitor.Text= First(Filter(ObjectDetector1.VisionObjects,StartsWith(displayName,”Monitor”))).count

lblMouse.Text= Last(ObjectDetector1.VisionObjects).count

You can make your own formula by utilizing the Gallery or Object Detector controls

e. Insert a Create button. Click on Create button, navigate to Action > Flows > Select the existing flow or Create a new Flow as described in 3^rd point. It will start processing and add the selected flow to PowerApp.

Modify the function of Onselect as shown below by passing the parameters to the flow. Here, CreateElectronicEntry is the name of flow.

OnSelect =CreateElectronicEntry.Run(Concat(Gallery1.AllItems,displayName & “-” & count & “,”),lblMobile.Text,lblKeyboard.Text,lblMonitor.Text,lblMouse.Text)

f. Save and Publish the App.

3. Pass data from PowerApps to Dynamics 365 CRM using Microsoft Flow

You can pass data to Dynamics 365 CRM using the Patch statement on click button in PowerApps itself but here we are showing it using a flow because Microsoft flow has many capabilities and you can perform so many tasks by connecting your app to different connectors depending on your business requirements.

a. Create a new instant Flow with trigger of PowerApps.

b. Add New Step >> Search for an Action ‘Common Data Service’ >> Create a New record.

c. Select your ‘Environment’ and ‘Entity Name’. We have created another custom entity ‘Electronic Entry’ which has the fields Monitor, Keyboard, Mobile and Mouse which shows the count of these devices.

d. Map the fields by clicking on ‘Ask in PowerApps’. It will automatically map relevant PowerApps fields with the CRM fields.

e. Save the flow.

4. Run the App

You can capture an image from your mobile camera or select an existing image from Gallery. Click on the Detect button. The objects will be identified if it matches with trained objects and the list would show count of each object detected in the image.

When Create button is clicked it triggers the flow which creates a record in CRM as shown below: –

Conclusion

In this way, you can build AI Object detection App which is an easy to use tool, just point and click, to tailor AI in your business as per your requirements. Object Detection lets you to count, locate and identify selected objects within any image. You can use this model in PowerApps to extract information from pictures you take with the camera.

Please visit the Source and support them

The post Power Platform: How to Build AI Object Detector using Power Platform appeared first on Microsoft Dynamics 365 Blog.

It is well-known that Power Automate is a low-code, no-code solution to automation with various triggers that it supports including Event driven, HTTP request, Timer/Scheduled and Manual flows.

Manual/Button flows help in designing powerful Canvas Apps that can offload complex logic executions to flow while focusing on user experience of the app. In this article we will discuss an example to call a flow and pass user inputs received in Canvas Apps to the flow – have the logic execute there and return resulting value to the Canvas Apps for display.

In this example, we have a canvas app that accepts requested meeting time, the app then calls the flow to check availability for the said time, if the time slot is unavailable, it will return false to app to notify the user accordingly.

I have shared the key settings to achieve this by using Case entity from Dynamics 365 CRM. A quick design of the entry form is given below:

Note the customer field when placed on form does not show up the field on Canvas for data entry. Lookup fields are not currently supported. Here is how I got this to work:

Select the Data card created for Customer when you include that field on the form from tree view and then choose Insert Drop Down.

Set the properties of the drop-down as shown below:

Items = Sort(Accounts,’Account Name’) – This will show the list of accounts sorted by name.

With the Customer_DataCard3 still selected in the tree view add a Label and set the name to ‘Customer’.

With this done, we now get the drop down of accounts listed. However, the value selected in the drop-down will not be submitted as the value for Customer Card and therefore will not be saved in database when we submit the form.

To be able to edit the property to the Card, we need to first Unlock it by clicking on lock icon.

Next, we edit the Update property of card to set the value as Dropdown1.Selected as shown below:

With this done, any change in the value of dropdown will bind the selected value to the customer property.

Next let’s work on designing the Power Automate Flow that need to call to check availability.

For this, choose the OnSelect property of Request button and choose Action à Power Automate to bring up the following screen.

As we do not have our flow already designed, we choose ‘Create a new flow’ which navigates us to the flow designer.

Type PowerApps in the connector search bar and select the PowerApps trigger.

This would be the trigger to be used to invoke the flow from Canvas Apps. Do note that only flows that are based on PowerApps trigger would show up in the Power Automate action list for selection.

Here is a screenshot of a very simple flow designed for this blog.

In order to generate a parameter for the flow, choose the ‘Ask in PowerApps’ option from Dynamic content. This will auto generate a parameter for you for the base time field as shown below.

In order to return a value back to the calling App use the action ‘Respond to a PowerApp or flow’.

Now set the value you need to return. Define the data type that you want to return by clicking on ‘Add an output’.

Note that you could return more than one value back to the calling App. It is received in the calling app in the form of a record with each output parameter name as a field in that record.

Save the flow and now let’s move back to the canvas app to call this in our app.

On the Request button in canvas app, we pass the date value selected in the First Response By field and send it to the flow as a parameter for evaluating availability. The flow returns a Boolean value based on its evaluation.

Set the following on the OnSelect property of Request button.

Set(Available, ‘PowerApp->Performanunboundaction,RespondtoaPowerApporflow’.Run(‘First Response By_DataCard1’.Update));If(Available.result,SubmitForm(Form1);NewForm(Form1), Notify(“Invalid date entered”));

Using Set() function we are storing the return value from the Flow to the variable named Available.

‘PowerApp->Performanunboundaction,RespondtoaPowerApporflow’.Run(‘First Response By_DataCard1’.Update))

In the above statement, we make a call to the Power Automate Flow and pass the value of the First Response By field.

Notice, we access the output parameter returned from flow as

Available.result – where result is name of the output parameter defined.

This now completes the canvas app, and you are ready to test it by entering values in the app.

Notes:

1. Begin designing the canvas app and flow from within the context of a solution
2. Work with the Common Data Service (Current) connector.
3. When Perform Unbound Action action is added, we are unable to invoke the flow from the Canvas Apps, this problem could be solved using Child Flows!!

Conclusion

In this way, we would be able to design a Canvas App (no-code) and have the business logic execute written as a Custom Action (pro-dev) by using a (no-code/low-code) Flow – The no-cliff solution to building powerful apps.

Please visit the Source and support them

The post Interacting with Power Automate Flows from Power Apps – Canvas Apps appeared first on Microsoft Dynamics 365 Blog.

In the previous blog, we obtained the response from the Relevance Search API request through Power Automate Flow. In this blog, we will use that response in the Canvas app. We will see how we can leverage the potential of Relevance search in the Canvas app.

If you are not familiar with how to create Canvas app then you can refer the following article,

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/get-started-test-drive

Let us start with creating a new canvas app,

• Sign in to https://make.powerapps.com and create a new Canvas app.

• As we are going to create Canvas app for Dynamics 365 app, we will select the Common Data Service Phone Layout,

• In the next screen, we will first add the connection then add the table.

• This will create a canvas app with default Browse, Detail and Edit screen. As we are going to work with Contact and lead, we added the screens for Lead and Contact.

• We will now add a new screen for the Relevance Search, like shown below

• We will call Power Automate Flow that we have created in the previous blog upon OnSelect of the Search button and upon OnChange of the textbox.

We will use below expression OnSelect of the button and on OnChange of the textbox.

This expression will run the ‘RelevanceSearchAPIFlow’ and will pass the text entered in the TextBox. After successful run, it will store the response in the Collection called “SearchCollection”.

• Save and run the App. Enter some text in the Textbox and either click enter or click on the Search Button. In the background, a Power Automate Flow should run successfully and response should get stored in the ‘SearchCollection’ collection.

• To check the collection, click on View -> Collections

You should see the response added in the collection.

• Now we will use this collection to bind to the List control. Select the List control and add the below expression to the Items property,

Here we are assigning non-empty items from the SearchCollection collection to the List control.

• After this, select the List control and add below expression OnSelect property of the control.

Here we are extracting and setting the GUID of the record that we have in the collection to the ‘SelectedItemID’ variable.

• We will now bind the record values to the list item. Select the first label and add below expression,

Here we are binding the primary field value of the record.

Similarly, select the second label and add below expression,

Here we are binding the Entity logical name to understand the entity type of the record,

• Select the ‘NextArrow’ button and add below expression upon OnSelect property,

Here we are first setting the GUID of the record to the SelectedItemID variable and then switching the Detail screen based on the Entity logical name. For example, if the entity is Contact, we are navigating the screen to DetailsScreenContact_1 and if the entity is lead, we are navigating to the DetailsScreenLead_1 screen.

• Now select the Detail screen where we will see the details of the record. Add below expression to Item property of the DetailScreen,

This expression is for the contact screen,

Similarly, add expression for other details screen,

This expression is for the Lead screen,

• Here we have setup the detail screens of lead and contact to show up the record details on click of the Search Results item from Relevance Search Screen.

Relevance Search screen,

On click of the next arrow button, it will open the appropriate entity record.

• You can add entities that you need and you can add fields to show up in the detail screen or the search result.

This way we can execute the Relevance search API from Canvas App and represent the Search results using List control.

Conclusion

You can use the logic explained in this blog to add Relevance search into your Canvas app.

Below is the small clip of the working Relevance Search screen,

Please visit the Source and support them

The post Use Relevance Search API in Power Automate & Canvas App – Part 2 appeared first on Microsoft Dynamics 365 Blog.

Recently Microsoft has released the preview of the new horizontal and vertical container in the Canvas apps layout. While building the apps it is essential that apps are uniform and responsive within any type of device or different screen sizes for an optimized user experience. These layout containers improve the creation of responsive apps with less effort.

Let’s see how we can use this layout container in our apps.

To enable this feature:

1. Go to the respective app and navigate to the File > Settings > Advanced Settings > Enable Layout containers as shown below:

Note: The Horizontal and Vertical Container feature is in preview.

2. Also, make sure to disable the below setting and click on the Apply button:

Then, go to the Home screen > Insert > Layout > Horizontal container and add it to the canvas. This will add the blank layout on the canvas and we can add containers inside this layout.

Or, we also get three new screen templates as Split-screen, Sidebar / Header, Main Section, and Footer with the prebuilt responsive capabilities as shown in the below screenshot. To get the screen template, go to New Screen, select the required screen, and add it to the canvas.

For instance, I have selected the Sidebar screen, it will automatically add multiple containers on the canvas. I have designed my app by adding the Account entity as a data source. When we select any container, it opens the Properties window where we get the options to properly align the controls.

So whenever we resize the browser, the app automatically gets aligned according to the size. See the below screenshot for reference:

Conclusion

Using these new horizontal and vertical containers in the Canvas apps layout, users can create responsive apps to ensure a great user experience.

Please visit the Source and support them

The post How to Build Responsive Canvas Apps appeared first on Microsoft Dynamics 365 Blog.

Recently we needed to trigger Power Automate flow from Javascript later after reading my friend's Blog (Ajit Patra Link below) we decided to have a Button which will execute power automate flow using JavaScript.

It was presented as On-demand Power Automate flow to System user

Please go through Referred Ajit’s Blog  for more detail, where he explained how to Execute PowerAutomate on click of a button on the Lead record

Below is Demonstrated in below part

1. Create Power automate Flow to receive HTTPS Request from Javascript and send Email
2. Register Javascript
3. Creating a Ribbon Button on Contact Entity and add javascript action to the button Command and pass PrimaryControl

The post Execute Microsoft Power Automate from Ribbon using JavaScript – On demand Power automate flow using Javascript – in UCI – Replace RibbonAction.js appeared first on Microsoft Dynamics 365 Blog.