As Microsoft is providing us more flexibility with Power Automate (MS Flow), now we can retrieve List of solution details and their components directly within Power Automate flows.

Recently, we got a requirement to retrieve the list of solutions and their components from specific environments and store this information in an Excel file on SharePoint.

We can achieve this using Solution and Solution Components entity records in Dynamics CRM.

Below are the steps to achieve this requirement.

Step 1: Initialize the Array variable

This array variable should include the details of the solution component types you want to retrieve from the solution, as shown in the screenshot below.

The above array contains the following details of the solution component types:

• ComponentType – The type value of the component from the documentation.
• EntityName – The logical name of the component type.
• FilterRowName – The field name to filter the component type.
• SelectColumn – The field name to filter the component type.

You can find all solution component types information in Microsoft Documentation

Step 2: Retrieve solutions

Add the ‘List rows from selected environment’ step to retrieve the solutions from the specific environment. Use a filter query to retrieve the visible solutions and exclude the default solution.

Step 3: Retrieve Solution Components

Now, proceed to retrieve the solution component for the previously obtained solution. Utilize an ‘Apply to Each’ step to iterate through each solution, and within that, add a ‘List rows’ action to retrieve the solution component using the filter rows.

Step 4: Filter Array step to check the Component Type

For each solution component, implement an ‘Apply to Each’ loop. Inside this loop, use a Filter Array step to check that the Component Type of the current solution component matches the type specified in the array variable we set up earlier.

Expressions from the above image:

• variables(‘SolutionCompentSummary’)
• @item()[‘ComponentType’]
• items(‘Apply_to_each_Solution_Components’)?[‘componenttype’]

Step 5: Retrieve Solution Components Summary

Add the ‘List rows’ step to retrieve the solution component if the Component Type matches and add a row into the Excel table.

Expressions from the above image:

• length(body(‘Filter_Solution_Component_Summaries’))
• body(‘Filter_Solution_Component_Summaries’)[0][‘EntityName’]
• body(‘Filter_Solution_Component_Summaries’)[0][‘FilterRowName’]

Expressions from the above image:

• items(‘Apply_to_each_Solutions’)?[‘uniquename’]
• items(‘Apply_to_each_Solutions’)?[‘createdon@OData.Community.Display.V1.FormattedValue’]
• items(‘Apply_to_each_Solutions’)?[‘version’]
• items(‘Apply_to_each_Solutions’)?[‘ismanaged@OData.Community.Display.V1.FormattedValue’]}
• outputs(‘List_of_Solution_Component_Summary’)?[‘body/value’][0]?[body(‘Filter_Solution_Component_Summaries’)[0][‘SelectColumn’]]
• concat(toUpper(take(replace(string(outputs(‘List_of_Solution_Component_Summary’)?[‘body/value’][0]?[‘@odata.type’]), ‘#Microsoft.Dynamics.CRM.’, ”), 1)), toLower(skip(replace(string(outputs(‘List_of_Solution_Component_Summary’)?[‘body/value’][0]?[‘@odata.type’]), ‘#Microsoft.Dynamics.CRM.’, ”), 1)))

Conclusion:

By following these steps, you can retrieve Solutions and their component details using Power Automate flow.

From customizing Microsoft Dynamics 365 to developing Copilot-enabled Power Platform Apps, our outsourced development services ensure top-notch solutions tailored to your needs. Let our experts handle the technicalities while you focus on your core business. Email us at crm@inogic.com to get started today.

The post List solution details and their components using Power Automate Flow first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post List solution details and their components using Power Automate Flow appeared first on Microsoft Dynamics 365 Blog.

I needed one URL that would trigger on “GET” and “POST” methods. Only one time it will trigger the “GET” method to validate logic and after that, it will call for the “POST” method to process some response. Below is the approach that allowed us to fulfill the client’s requirements seamlessly.

1. Create a solution in https://make.powerapps.com/where you have to add your Power Automate (Ms Flow)

2. In the solution click on the “New” button & select Flow as shown in the below image. It will redirect you to the Power Automate (MS Flow) window as shown in the following image.

3. Now we have to Search for the “When an HTTP request is received” Trigger point in our newly created Flow & from the search result select “When an HTTP request is received” and select “Who can trigger the flow” from the dropdown as per your requirement configure “Who can trigger the flow” based on your needs. Set the method as “GET” and give your flow a name. Finally, click on “Save” to obtain the “HTTP POST URL”.

4. Once saved, you’ll receive an HTTP POST URL, as illustrated in the image below. Now I am using this URL as the endpoint. This ensures that whenever it is triggered, your flow will also be triggered, regardless of whether the request is a “GET” or “POST“.

5. Next, add the “Initialize Variable” action to create variables. It will store the data coming into the Body.

6. When the “GET” method is called then Body will be blank, we will get a result from query string parameters however in the “POST” method response will come in Body. So, to handle both scenarios I have added the condition to check If Data is null then it should move further and take query string parameters and return them in the response as well as update that Power Automate from the “GET” method to “POST” else it will direct return the response.

Whenever any Power Automate gets created those are stored in the “workflow” entity. So, I tried to find my Power Automate using ODATA and I got its ID, name, and other details. It stores all Power Automate steps in one field “clientdata” in JSON format. So, to update from “GET” to “POST” we need to follow the below steps.

Now in Power Automate, we specified the table (entity) name as “Processes” which is the display name of the “Workflow” entity, and entered the ID of our flow in the “Row ID” field. we also need to retrieve the method stored in the “clientdata” attribute column. Therefore, select “clientdata” in the “Select columns” option. Also, set the variable “RecordData” using the “Body” output of the “Get row by ID” action.

7. Following this, use the “Compose” action, where the input will be modified by substituting “GET” with “POST” in the aforementioned JSON.

8. The subsequent step involves parsing the JSON, which means converting the JSON string into an object format. It’s essential to input the correct schema, as illustrated in the image provided.

9. The final step involves updating the previously retrieved process record. Modify the “clientdata” column to reflect the updated “clientdata”, wherein the method has been changed to “POST“.

10. After the record is updated, the modified JSON will resemble the image below.

Conclusion

In conclusion, the method outlined above demonstrates how you can dynamically alter the flow’s method from “GET” to “POST”. This is particularly useful when there’s a requirement for your flow to be triggered once using the “GET” method and subsequently, for all future triggers, to operate using the “POST” method.

The post How to configure a trigger to handle both GET and POST requests effectively using Power Automate first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post How to configure a trigger to handle both GET and POST requests effectively using Power Automate 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.

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.

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.

Here I will share one of my business case scenario using Power automate, Excel and OneDrive for a conference management that can be apply to all other training class scenarios.
we normally want to create a personalized folder for your students in class or for our speakers in a conference so they/we can put or files there and be separated environment from others. Or at the same time we want to send a specific email for each of the people based on their situation.

Of course writing codes in C# is one way, but there are other way without writing code is available for someone like me that did not write C# code for some years or event never right code.

Excel Part

The first step was to create the list, I create a online Excel File to store speakers name and email in table format excel file and I put it inside my OneDrive folder.

Then, I enable one Add on inside Excel online named Flow. To access it first click on the Insert tab, then in Office- Add-ins, navigate to Store and search for Microsoft Flow.

After enable the Flow Add-ins, you need to sing in to the Power Automate ( Microsoft Flow)

Now you ready to create your first flow section that is about creating a folder with name in the Excel sheet.

Flow Section

In the Microsoft Flow, you need to add a trigger so the flow and the process start.

The trigger for my flow is when a user select a row in the excel file. so if the end user select a/multiple row/s that contains the name, ID and the email of the speakers the trigger start.

For a selected row is my trigger. I need to specify the location of the Excel file in OneDrive as below and the Table name ( Make sure the data in the excel file are in Table format before)

In the next step, as we do not have and Action in Flow to create a folder, I follow the article by BUILDBOD.

So I create a temporary file with a folder name ( my desire name come from excel file), as the folder does not exist, so to create a temporary file, Power Automate, create a folder in that name, then I will delete the temporary file. As you can see in the below picture, Create file in OneDrive, the Folder Path is the desire folder, but I put the Name received from selected row in Excel ( Name of person in this example Leila Etaati). IN the next stage, a file with that Name also created, that in the next Action I delete it using Delete File in OneDrive.

That is all! for creating Folder. you can test is as below.

Next if you check your OneDrive you should see the folder has been created.

In next parts, I will show how to create a share link and how to send a customized nice message with images and personalized link to this created folder.

The post Streamline Sharing Folder and Email Message using Power Automate ( Part 1, Folder Creation) appeared first on RADACAD.

Follow Source

The post Streamline Sharing Folder and Email Message using Power Automate ( Part 1, Folder Creation) appeared first on Microsoft Dynamics 365 Blog.

In the previous posts ( Post 1, Post 2, and Post 3) the process of analyzing the forms using the Form processing feature in AI Builder has been explained.
from last month some changes happen in the Prediction module in Microsoft Power Automate that will impact the form processing experience using flow.
In this post, I will show you how to work with the new one. The previous of you created still working.
the changes happen in the Predict module.

What we Have

in the below flow we have a module Predict that has a Request Payload, and we need to specify the type of the image and the file as a string, also later we need to parse the result by another component name Parse JSON.

What to Change

Now everything gets a bit easier, we have a Predict module that in the separate box it gets the document type and document itself, next in the create type we just need to use the Concat function to get the result and values.

I have used the below code for the File Content:

concat(‘ Session Title: ‘,outputs(‘Predict’)?[‘body/responsev2/predictionOutput/labels/Session_85648318f538ad191ff5651a30c24966/value’],’ ,Speaker Name: ‘,outputs(‘Predict’)[‘body/responsev2/predictionOutput/labels/Speaker_64a30215a5867855cdcb495ee6eef3ec/value’],’ ,Comments: ‘,outputs(‘Predict’)?[‘body/responsev2/predictionOutput/labels/What_0027580d34b848d69176d3f4a73de5c5450/value’])

also, watch below video

The post Recent Update in Predict Module in Power Automate Predict- Part 4 appeared first on RADACAD.

Follow Source

The post Recent Update in Predict Module in Power Automate Predict- Part 4 appeared first on Microsoft Dynamics 365 Blog.

AI Builder brings a huge change to creating smart self-service Applications. In this post we are going to see how to create a smart application that able to read the Business Card content and extract them, then import them using Power Automate to the Outlook contact list.

Creat Business Card Reader using Power Apps and AI Builder

First login in the environment that supports the AI Builder.

Now in the new  Canvas app, create a new Phone layout

In the new page, click on the Insert option, then click on the AI Builder –> Business Card Reader

In the next step, click on the Insert Lable, and for the label write the below formula, BusinessCardReader1.FullName

Copy and paste two times for the email and Phone number

BusinessCardReader1.Email

and

BusinessCardReader1.BusinessPhone

Next, Save the App and Navigate to the Power Automate (Microsoft Flow)

Create Flow in Power Automate

Now navigate to the same Environment in Power Automate with the same account, First, create a new Flow, and the trigger should be Power Apps that do not get any input from the Power Automate,

Next, click on the Next step and add the “Create contact(V2)”

we need to set up some part of this component.

First the Folder ID, for me is Contacts

Next, the Given Name which is mandatory, click on the box, choose to Ask in Power Apps, then another component fir the GivenName will show choose that one and remove the Ask in pOwer APPs, do the same for the Home Phone and Email address

Then save the Flow and back to the Power Apps

Connect the Power Apps and Power Automate

Back to Power Apps to connect the Apps with Power Automate. Click on the Insert, then click on the button, and change the name of the Button to the Add

Next, click on the Button, then Action, then Power Automate, and in the list at the right sides of the page choose the Flow you just created, then at the formula bar you should it.

The list of required parameters has been listed also there.

Next, add the parameters as below

GettheContact_powerapps.Run(BusinessCardReader1.FullName,BusinessCardReader1.BusinessPhone,BusinessCardReader1.Email)

As you can see all the elements we already add in the Flow to be added in the Contact have been requested here as input parameters.

Run the application using the Run button at the top right

you should see the details and also you should see the contacts have been added to the contact section in outlook

see the video from here

https://youtu.be/lcQoQOhw_uA 

The post Business Card Reader Automation with AI Builder, Power Automate and Power Apps appeared first on RADACAD.

Follow Source

The post Business Card Reader Automation with AI Builder, Power Automate and Power Apps appeared first on Microsoft Dynamics 365 Blog.

Another exiting new update in AI Builder is Form Processing. With for Processing you able to train the model with forms you have and AI builder able to detect each session of the form and the related values. This feature is so exiting form as for 5 years I am one of the organizer of SQL Saturday Auckland and always I have challenge with evaluation. In some strange way people prefer to evaluate the sessions via paper rather online link. So I need to create an application with cognitive service that able to detect the elements in a form. Such as title of the session, speaker name and the comments from the attendees. In this post and the next one, I will explain the process from creating the form processing model to Flow application that helps me.

in this post and next One, I will explain the process.

First: Set up the Form Processing in AI Builder

Before start Make sure

! Make sure you have forms and at least 5 forms with less than 4 MB size and if it is handwritten form, the quality of form in jpg/png or PDF make sure to be good.

! You already access to AI Builder environment see Post. 

Now, you can start logging into the Power Apps make sure to access the environment you can see the AI Builder. You should see the AI Builder icon in left side of the window.

Next, under the AI Builder, choose the Build Option, then from AI model, choose the Form Processing.

In the new page, Form Processing put a name for the Model Name then select the create

The first step is Analyse Documents, you need to import at least 5 samples of the filled form you have. Just make sure the quality be good and the size of all file does not exceed 4MB.

As I mentioned before, I want to use this form processing for the aim of session evaluation, so I import 6 different session evaluation like below :

After importing the forms, you need to analyse the documents, so AI Builder can detect each section of the forms and related values.

Analysing the form take a couple of minutes, after that, you need to check the identified fields and choose the one that is matter to you

As you can see in the below picture, in this example three fields have been identified, and you able to see the confidence of each part by hovering your mouse over each field. Choose the fields you are happy about. The selected fields will be shown in the right panel.

After selecting the fields, you are in the second step of building form processing, to navigate to the third step, click on the Next.

Now, you imported your sample forms, at this stage you can train your model, you can see a summary of the model as the number of forms and number of selected fields. Then click on the Train option to navigate to the last step.

Training will take about a couple of minutes, depends on the number of documents for training, after training complete, Go to details page.

In the details page, you can see the number of documents you uploaded for training, the number of detected fields in each form, You can also test the model and then publish it.

for testing the mode, you need to import a sample of the form that you have, then wait to see the result in the Quick Test page.

In the sample, all trained fields should be identified. Next Back to the details page and Publish the model so you can use it in other applications

I want to create a workflow so I can upload pictures in OneDrive, then using this model and store back to OneDrive the result as a text file so I can use it Power BI report. As a result, after creating a model, I navigate to the Microsoft Flow. and I log in in the same environment I created the form processing model.

To make sure I can see the model I just created in Microsoft Flow, click on the model and you should see the Form Processing model is available with Publish Status as Live.

In the next post, I will explain how I create a Workflow that able to read scanned file from the OneDrive folder then apply the created model and store back in a text file in the OneDrive again.

The post Form Processing Work flow- Create Form Processing Model Part 1 appeared first on RADACAD.

Follow Source

The post Form Processing Work flow- Create Form Processing Model Part 1 appeared first on Microsoft Dynamics 365 Blog.

As I mentioned in Post 1 and Post 2, AI builder is a game-changer in Power Apps and Flow, it provides the facility to easy embed AI in applications and process without writing any code. Also, there is no need to set up other environment and applications to make it work.

In this post, I am going to show you how to activate your Power Apps trial account to see and practice the AI Builder.

There is some note:

AI Builder in Power Apps available in Europe and the USA region.

There is a Trial (29 Days) and Production plan

for this scenario, I choose the USA and Trial plan to examine the AI Builder

Set Up Environment in Power Apps

To setup, the environment needs to login into Microsoft Power Apps Portal. Login

In the next step, you need to navigate to the Gear icon at the top, then click on the Admin Centre

this, navigate you to the admin centre environment.

As you can see in the environment page, all of my available account under RADACAD has been shown with their type, region and name. As the default region for RADACAD account in Australia, and AI Builder for now just available in USA and Europe, I need to create a new environment.  In this new page, you will see the Environments option.

In the new page, you need to provide the environment name, region ( in my scenario I choose the USA) and the environment Type.

It will take a couple of seconds to create the environment, and you will receive a message about it as well.

After creating the new environment to access to AI Builder, you need to create a database in Common Data Services(CDS)

another important note

AI Builder need to access to Common Data Service

Click on the Create database.

During the creating the database, it will ask you about the data filed for Currency and Language. in CDS, you able to mention, if you have a currency field what currency be the default one, or in what language you want to store your data.

after setting up all required parameters click on the Create database so your new environment access to CDS. Now you able to see the new environment with the name AI Builder 

Now you need to back to Power Apps main page, click on the Environment dropdown at the top, and select the AIBuilder option. As you can see in the below picture, on the left panel, the AI Builder (Preview) has been shown.

after setting up the AI Builder for Power Apps, you can see the same functionalities in Microsoft Flow.

you need to Login to Microsoft Flow,

at the top right click on the account name, and choose the environment that you already set up for  AI Builder. The same as Power Apps, you able to see the AI Builder on the left side.

to see how AI Builder Works see Post 2 and also more post on it coming soon.

Special thanks to Joe Fernandez from Power Apps team to help to examine these features.

1- https://docs.microsoft.com/en-us/power-platform/admin/create-environment 

The post Activate AI Builder In Power Apps and Microsoft Flow appeared first on RADACAD.

Follow Source

The post Activate AI Builder In Power Apps and Microsoft Flow appeared first on Microsoft Dynamics 365 Blog.