dataverse metadata

Check Metadata of your Dynamics 365 instance in the browser | [Quick Tip]

priyeshwagh777 Dynamics 365 CE, dynamics 365 customization , , ,

If you are a newbie developer on Dynamics 365 Customer Engagement Applications / CRM, and you’ve been told to check metadata to verify if your customizations are in place or not, here’s how you can check the metadata –

This approach is without use of any managed solution or browser extensions.

Get Service Root URL

Here’s how you can get the Service Root URL of your environment once you have the System Administrator or System Customizer role –

  1. Drop down from Settings and look for Customization.

  2. And in Customizations, you can look for Developer Resources.

  3. You’ll find the Service Root URL mentioned in the Developer Resources page.

  4. Copy that and paste it in the browser – [Make sure you are always logged into the environment]

  5. Now, add the $metadata keyword to get the complete metadata of the environment.

  6. And when you press Enter, you’ll see the complete metadata.
    In case you don’t have enough memory on the browser due to cache issues, you’ll see this.


    In this case, you can either clear cache or try another browser. This will take some time to load.
    And you’ll see the metadata as below – you can then use Ctrl + F (Find) on the browser to look for the resources you are looking for

Hope this was useful!

Here are some Power Automate posts you want to check out –

  1. See Trigger Outputs using Edit Columns in Flow Runs | Power Automate [Quick Tip]
  2. Adding Image field on the form in Dynamics 365 CRM | Power Platform Modern Form Designer [Quick Tip]
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Advertisement

Reflecting Metadata changes in Flow for Dataverse connector

priyeshwagh777 Microsoft PowerApps , ,

If you’re building a Flow that uses Dataverse connectors, you might need to change the metadata and it doesn’t reflect in the Flow and the issue continues to occur even after publishing the changes.

Scenario

Let’s suppose you are using Add a row action to create a new record in Dataverse/Dynamics CRM –

  1. And when the Flow runs, the record is not created because you end up having this error where the length of the field enough to store the data.

  2. Now, in order to fix this –

  3. Now, even after I changes the above length – the error still occurs.

Issue

Let’s look at the issue –

  1. The issue is, at the time of creating the step, Flow stores the metadata with an ID and when you change the metadata in the backend, it is not reflected back on the Flow.

Workaround

Here’s what you need to do in order to fix this –

  1. You need to delete the step and re-do the step in your Flow

  2. And now, it will have the latest metadata with the new Metadata ID to it –

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobile app
  2. Create a Power Apps Per User Plan Trial | Dataverse environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  4. Co-presence in Power Automate | Multiple users working on a Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  7. Call a Flow from Canvas Power App and get back response | Power Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  10. Asynchronous HTTP Response from a Flow | Power Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  12. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!