web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Power Automate flow to...
Customer experience | Sales, Customer Insights,...
Answered

Power Automate flow to change Object type and regarding case on a Note attachment

(2) ShareShare
ReportReport
Posted on by NicholasHE 70
I have a Flow set up to create a new Case and Contact when someone submits a new form. The flow copies the description of the form body into the new case, but I am stuck on how to move the attachments across to the new case.
 
I have an Apply to Each action set up to update the rows in the Notes table. I know the action step works when I configure it to only add text to the note description field, but when I set the Object Type to 'Case' and the Regarding Case to the Case unique identifier set in the Create Case step, the workflow fails with this error:

URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL.
 
Is there a special approach to update an existing Note attachment from one entity and type to another?
 
Edit: I have tried using the plural name in the Regarding Cases field, but the error is the same. Eg: Regarding (Cases): Cases(Case), where the case value is the incidentid output from the Create Case step.
Categories:
Microsoft Dynamics CRM
I have the same question (0)
  • Suggested answer
    Dharanidharan Profile Picture
    Dharanidharan 638 Super User 2025 Season 2 on at

    Fix the “ODataUnrecognizedPathException” error.

     

    You’re encountering this error because:

     

    1. You’re using an incorrect URL path when setting the Object Type to ‘Case’.

     

    2. The field (_objectid_value) must be set to the correct GUID.

     

    To resolve this issue, follow these steps:

     

    1. Instead of manually setting the Object Type to ‘Case’, use the RegardingObjectId (Case) option.

     

    2. Ensure that you’re setting the correct GUID during the Create Case step.

  • NicholasHE Profile Picture
    NicholasHE 70 on at
    Hi Dharanidharan, thank you for the suggestion.
     
    Do you mean not setting the 'Object type' field and leaving blank? Or by choosing the custom text or an expression?
     
    I believe the Case GUID is correct because when I inspect the relevant input after testing, I see this included, which is the correct GUID
    "item/objectid_incident@odata.bind": "Cases(be3a5aa9-7ffd-ef11-bae3-7c1e522a6fa7)"
     
     
  • Verified answer
    Dharanidharan Profile Picture
    Dharanidharan 638 Super User 2025 Season 2 on at
    Since the GUID is correct, the issue might be due to the way the Regarding field is being formattted.

    you can try setting the Regarding field using an expression:

    concat('/incidents(', <Case GUID>, ')')

    instead of cases please set it as incidents

  • NicholasHE Profile Picture
    NicholasHE 70 on at
    Thanks again Dharanidharan, I think that was a a very good ide to use 'incidents' in the Regarding case field. There is a different error now, but on the Object Type field from the look of the error. This one is a mystery.

    The entity with a name = '112' with namemapping = 'Logical' was not found in the MetadataCache.LazyDynamicMetadataCache with version 11396502 and timestamp 11396502
     
    Update: I tried many variations but ended up just leaving this field blank in Power Automate, and the flow ran successfully, there must be hidden logic that sets this automatically based on the Regarding Case field setting. 

    Because your excellent other suggestion to change to Incidents fixed the other issue I marked that as the answer. But for anyone reading, my experience was to not set the Object Type field, and just leave blank in the automation.
  • Suggested answer
    Dharanidharan Profile Picture
    Dharanidharan 638 Super User 2025 Season 2 on at
    You're welcome! The new error "The entity with a name = '112' with namemapping = 'Logical' was not found in the MetadataCache.LazyDynamicMetadataCache" usually indicates that Power Automate is referencing an entity that does not exist or is misconfigured.
     
    Possible Causes & Fixes:

    1. Check If the Entity ID (112) is Correct
    • Go to XrmToolBox -> Open Metadata Browser and connect to the Dynamics 365 CE instance.
    • Look for an entity with ID 112.
    • If it's missing, Power Automate might be referencing a deleted or unrecognized entity.
    • Fix: Update the Flow to reference the correct entity.
    2. Refresh Metadata in Power Automate
    • In Power Automate, open your Flow.
    • Locate the Dataverse (or Common Data Service) action.
    • Re-select the table/entity from the dropdown (this forces metadata refresh).
    • Save and test again.
    3. Check the Object Type in "Regarding" Field
    • If you are using "Regarding" to relate the record to a Case (Incident), ensure that the Entity Type is set correctly.
    • Fix: Verify that you are using the correct Table Name (Logical Name) for Cases (incident).
    • If using a dynamic value, ensure it resolves to the correct entity.
    4. Update Flow Connections
    • Open Power Automate.
    • Go to Connections and verify that the Dataverse connection is valid.
    • If needed, remove and re-add the connection.
    5. Check for Recent Solution Updates
    • If there was a recent solution import or deployment, the metadata cache might be outdated.
    • Fix: Refresh the cache by going to Advanced Settings > System Jobs > Metadata Refresh (or restart Power Automate).
    6. Hard Reset Power Automate & Test Again
    • Turn Off the flow.
    • Wait a few minutes and Turn it Back On.
    • Test by manually triggering a record creation/update.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 170 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 61

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 52 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans