Dynamics Community Forum Thread Details

Hello CU06031700-0,

You're encountering a common error when integrating Microsoft Forms with Dynamics 365 via Power Automate, specifically related to how you're handling lookup fields (like currency) and date fields (like estimated close date). Let's break down the problem and find a solution.

Understanding the Error:

The error "URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL" usually means that:

Lookup Fields: You're trying to set a lookup field (like currency) using a value that doesn't match the expected format (an OData link to the related record).
Date Fields: You might be formatting the date incorrectly, or the date value is not being passed in the expected format.

Troubleshooting and Solutions:

Currency Lookup:
- The Problem: Currency is a lookup field in Dynamics 365. You can't just pass the currency name or symbol. You need to pass the OData link to the currency record.
- Solution:
  - Get Currency ID:
    - Before creating the Dynamics 365 record, use the "List rows" (Dataverse) action in Power Automate to retrieve the currency record based on the currency name or symbol from your Microsoft Form.
    - Filter the "List rows" action to find the currency you need (e.g., filter by "Currency Name" or "Currency Symbol").
    - Get the currencyid from the retrieved currency record.
  - Format the Currency Lookup:
    - In the "Create a new row" (Dataverse) action for your Dynamics 365 record, use the following format for the currency field:
      - "/currencies(<currencyid>)"
      - Replace <currencyid> with the dynamic content from the "List rows" action.
- Example: If your currency id is: 12345678-1234-1234-1234-123456789012, then in the currency field in the create a new row action, you would enter: /currencies(12345678-1234-1234-1234-123456789012)

Estimated Close Date:
- The Problem: Date fields in Dynamics 365 expect a specific date format.
- Solution:
  - Format the Date:
    - In your Microsoft Form, make sure the date field is set to a date type.
    - In Power Automate, use the formatDateTime() expression to format the date from your Microsoft Form into the correct format.
    - The most reliable format is yyyy-MM-ddTHH:mm:ssZ (ISO 8601).
  - Example:
    - If your Microsoft Form date field is called "CloseDate," use the following expression in the "Create a new row" action:
      - formatDateTime(outputs('Get_response_details')?['body/r0020120123123123123123'], 'yyyy-MM-ddTHH:mm:ssZ')
      - Replace outputs('Get_response_details')?['body/r0020120123123123123123'] with the actual dynamic content from your Microsoft Form.
  - If you are only sending the date, and not the time, then the format yyyy-MM-dd will also work.

Other Lookup Fields:
- If you have other lookup fields in your Dynamics 365 record, apply the same logic as the currency lookup.
- Use the "List rows" action to retrieve the related records and format the lookup values correctly.

Data Type Mismatches:
- Double-check that the data types of the fields in your Microsoft Form match the data types of the corresponding fields in Dynamics 365.
- Mismatches can cause errors during record creation.

Create a new row (Dynamics 365):
- If your Microsoft Form fields can be empty, handle those cases in your Power Automate flow.
- Use "Condition" actions to check if the field values are empty and set the corresponding Dynamics 365 fields accordingly.

Example Flow (Conceptual):

Trigger: When a new response is submitted (Microsoft Forms).

Get Response Details: Retrieve the form response data.

Get Currency:
- "List rows" (Dataverse) to find the currency record based on the form's currency selection.

Format Close Date:
- formatDateTime(outputs('Get_response_details')?['body/r0020120123123123123123'], 'yyyy-MM-ddTHH:mm:ssZ')

Create a new row (Dynamics 365):
- Set the currency field to "/currencies(<currencyid>)" (from the "List rows" action).
- Set the close date field to the formatted date.
- Set other fields from the form response.

Key Points:

Lookup fields require OData links.
Date fields need to be formatted correctly.
Handle null or empty values.
Test thoroughly.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Community site session details

Connecting Microsoft Form to Dynamics 365 Opportunity - getting around "currencies"

Helpful resources

Quick Links

Mansi Soni – Community Spotlight

Announcing our 2025 Season 2 Super Users!

Congratulations to the July Top 10 Community Leaders!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

Featured topics

Product updates