The post Setting up PowerApps Canvas with Dynamics 365 Data appeared first on Ellipse Solutions.

Source

The post Setting up PowerApps Canvas with Dynamics 365 Data appeared first on Microsoft Dynamics 365 Blog.

Follow the Source

The post Excuse me! API limits for Microsoft Power Platform Dataverse & Dynamics 365 (2023 Edition) appeared first on Microsoft Dynamics 365 Blog.

By default, you can pin/unpin the Note table records only as you can see below,

For any other activities if you want to enable the Pin/Unpin feature then,

• Navigate to https://make.powerapps.com/.
• Open the form of a table on which you want to enable the pin/unpin feature in the timeline. For example, the Account table as shown below,

• In the timeline properties, under ‘Activity types,’ select the desired activity, and then enable or disable the ‘Pin / Unpin’ feature for the same as shown below,

Once you pin the records, they will be displayed under the Pinned section in the timeline as follows,

Note: You can pin a maximum of 15 records, and they will stay at the top for a year unless you unpin them.

Conclusion:

Thus, summarizes the process of pinning and unpinning records to the timeline with PowerApps

The post Pin or Unpin records in the Timeline with PowerApps first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post Pin or Unpin records in the Timeline with PowerApps appeared first on Microsoft Dynamics 365 Blog.

Now you can easily search and filter the environments created in your CRM.

As you can see in the above screen clip, the default environment created is getting displayed under “Other environments” and the environments we create will be displayed under “Build apps with Dataverse”.

Also, you can filter your environments based on Role, Data Platform & Environment type as well:

Revert button on Product:

Noticed the newly added button i.e. “Revert” on the Product record revising the product? It allows the user to revert all the changes made in the product properties after clicking on the Revise button.

Note: Only changes made in the properties (new or existing) after revising the product will get reverted. If you have added any properties before revising products, those properties will not be reverted.

Download FetchXML is now available in the modern advanced find:

In our last blog where we talked about the new modern find feature, we had a complaint saying that Downloading FetchXML is not present. So here it is now!

Conclusion:

These newly added features in 2022 will surely make the user experience in D365 much easier.

Ps: Our favorite Community Summit is back trending with #MySummitNA – Eagerly awaiting to meet our CRM friends in person. Inogic will be at Booth #1334 at the Summit, Gaylord Palms, Orlando, FL from 10^th to 13^th October 2022. Do block your calendars for 12.15 pm on Oct 12^th for our Partner Solution Showcase session Maps for CRM – Maplytics by our CEO at Room Coastal 7 – Convention Center, Level 2. Register now using our Promo Code INOGIC10, and avail of 10% off on your registration! 

Please visit the Source and support them

The post A quick walkthrough of some eye-catching 2022 updates of PowerApps! appeared first on Microsoft Dynamics 365 Blog.

• You get an error – “msbuild is not recognized as internal or external command” while executing msbuild command from your regular command prompt
• You get an error – “msbuild is not recognized as internal or external command” while executing msbuild command from Visual studio code. 

  

  Step 1 – Go to properties of current machine This PC.

  

  Step 2 – click on Advanced system settings

  

  Step 3 – Click Environment Variable

  

  Step 4 – Edit Path Value

  

  Step 5 – Set the path

  For Visual Studio 2019 use below value.

  HTML

  %ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin

  For Visual Studio 2017 use below value.

  HTML

  %ProgramFiles(x86)%\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin

  

  Click in OK in all Widows and Done.

  Step 6 – Reopen Command Prompt or Visual Studio code and open terminal

The post ” msbuild is not recognized as internal or external command ” error PCF – msbuild error – msbuild is not recognized appeared first on Microsoft Dynamics 365 Blog.

Follow the Source

The post Now it is time to be Curious about Power Platform Environment Variables! appeared first on Microsoft Dynamics 365 Blog.

Do you have a Power BI dataset that gets data from a dataflow? have you ever thought; “can I get the dataset refreshed only after the refresh of dataflow completed and was successful?” The answer to this question is yes, you can. One of the recent updates from the data integration team of Power BI made this available for you. Let’s see in this blog and video, how this is possible.

The scenario

If you are using both dataflows and datasets in your Power BI architecture, then your datasets are very likely getting part of their data from Power BI dataflows. It would be great if you can get the Power BI dataset refreshed right after a successful refresh of the dataflow. In fact, you can do a scenario like below.

Power Automate connector for dataflow

Power Automate recently announced availability of a connector that allows you to trigger a flow when a dataflow refresh completes.

Choosing the dataflow

You can then choose the workspace (or environment if you are using Power Platform dataflows), and the dataflow.

Condition on success or fail

The dataflow refresh can succeed or fail. You can choose the proper action in each case. For doing this, you can choose the result of refresh to be Success.

Refresh Power BI dataset

In the event of successful refresh of the dataflow, you can then run the refresh of the Power BI dataset.

Refreshing Power BI dataset through Power Automate is an ability that we had for sometime in the service.

Capture the failure

You can also capture the failure details and send a notification (or you can add a record in a database table for further log reporting) in the case of failure.

Overall flow

The overall flow seems a really simple but effective control of the refresh as you can see below.

My thoughts

Making sure that the refresh of the dataset happens after the refresh of the dataflow, was one of the challenges of Power BI developers if they use dataflow. Now, using this simple functionality, you can get the refresh process streamlined all the way from the dataflow.

Dataflow refresh can be done as a task in the Power Automate as well. Which might be useful for some scenarios, such as running the refresh of the dataflow after a certain event.

This is not only good for refreshing the Power BI dataset after the dataflow, it is also good for refreshing a dataflow after the other one. Especially in best practice scenarios of dataflow, I always recommend having layers of the dataflow for staging, data transformation, etc, as I explained in the below article.

Although, dataflow is not a replacement for the data warehouses. However, having features like this helps the usability and the adoption of this great transformation service.

Do you think of any scenarios that you use this for? let me know in the comments below, I’d love to hear about your scenarios.

Video

The post Streamline Power BI Refresh: Refresh dataset after a successful refresh of dataflow appeared first on RADACAD.

Follow Source

The post Streamline Power BI Refresh: Refresh dataset after a successful refresh of dataflow appeared first on Microsoft Dynamics 365 Blog.

Follow the Source

The post What is API limit for Microsoft Dataverse (Common Data Service)? appeared first on Microsoft Dynamics 365 Blog.

Go to Source and Follow

The post Power Platform Hands-on Learning appeared first on Microsoft Dynamics 365 Blog.

Do remember, we have enabled AAD authentication for our Azure function.

The APP registration provided while enabling AAD authentication was set for multi-tenant authentication.

While we have an easy way to create a custom connector outside the scope of a solution, since we will also cover moving custom connectors from one environment to another, we will look at the steps to create the connector from within a solution

Navigate to https://make.powerapps.com and open your solution. Next, choose New > Other > Custom Connector.

First Step provide Connector details like name, image and short description. In the host add the host name of your Azure function i.e if your azure function url was

https://xxx.azurewebsites.net/api/GetTaxRate?code=xxxx

the host would be xxx.azurewebsites.net

Next comes security. Since we are looking for AAD authentication, we will choose OAuth 2.0 in this step.

Client ID = APP ID of the App registration created while setting the AAD security for Azure function

Client Secret = Secret key of the above app.

Leave the login url and tenant id as is.

Resource URL = Copy and paste the client id (app id of the app registration)

Ref: Why leave common in tenant id –  https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant

After you save the connector, the Redirect URL will be generated as shown above. Copy the redirect URL and we need to add this to our app registration (same one of which you have provided the client id here)

Next in the Definition tab, we will provide the details of the actions that we wish to expose through our connector

Under actions choose new action and provide the action details. The details entered here will be displayed to the user when using your connector and this action so make sure to have all the descriptive information included here.

In the request section click import from sample and provide the request details. You can copy the url from Postman where we had done the test call.

My request has 2 query parameters and in the header I need to pass the CRM connection details like URL and the Client ID, Secret for connection to the said environment.

When you click import, you will see all the query parameters and header information has been generated for you.

Click Update Connector to save all changes to the connector.

Before we test the connector we need to complete a few additional settings in Azure APP registration.

Completing the authentication settings on Azure AD APP registration

Navigate to Authentication section of the App Registration

Click Add a platform

Choose Web and paste the Redirect URI copied from the connector

Click Save to save this redirect uri.

Next navigate to the Expose an API setting of the APP registration and click add scope

Details provided here are displayed to the user when they are making a connection to our connector and are from another tenant. These details are used on the Consent screen

Test the connection for the connector:

Navigate to https://make.powerapps.com > Data > Custom Connectors

Click the + button against the connector to build a connection to it. When you click, you should be prompted to login to Azure AD

Enter the credentials, if you enter the credentials of an environment other than the current environment, you would be prompted with the following screen

Click Accept and you should have a successful connection object created for this connector.

Note sometimes, after this screen it may display you an error about app registration error. Try again and the next time it succeeds

Moving this custom connector to another environment

Since we added this connector to a solution, simply export the solution as managed solution and import it to the other environment.

Navigate to Custom connectors tab to find the connector listed there

Click the + button to test connection with the connector

If you get an error about invalid client id and secret key,

edit the connector and fill in the security page once again. It will be the same client id and secret key that we had added when creating this connector in the other environment.

Consuming this connector through Power Automate Flows

We are now ready to create a flow and add a step for the operation in our connector.

Choose Manual Trigger of flow

In the Custom tab, you should find our connector

Choose our action

And now provide the requested details in an end user friendly UI

And the result is

Source

The post Building Custom Connectors for Power Apps and Power Automate Flows – Part 2 appeared first on Microsoft Dynamics 365 Blog.