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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Suggested Answer

Can't associate an annotation to a case via regarding object

(2) ShareShare
ReportReport
Posted on by 12

Hi, I'm developing my ticketing application using Power Apps via a Canvas App. Users have the ability to add notes from the portal, which then flow into the timeline in the Customer Service Hub. However, although they can create notes, they are currently unable to create notes associated with a case because I don't know how to populate the "Regarding Object (Case)" field in the Power Automate workflow. At the moment, I have entered the case ID, but apparently, it is not linking correctly. I have also tried to populate it with OData ID, but this is giving me an error too.  What is confusing me is that, checking out my annotation table on Dataverse, the field "Regarding Object" is filled with the following icon, which is not giving me any information on what value to fill in my flow.

Screenshot 2025-03-26 160312.png
I have the same question (0)
  • Suggested answer
    Khushbu Rajvi. Profile Picture
    22,792 Super User 2026 Season 1 on at
  • Suggested answer
    Ramesh Kumar Profile Picture
    7,561 Super User 2026 Season 1 on at
    Hi,
     
    I hope below link can help you review the issue
     
     
    Thanks
    Ramesh
     
    If this was helpful, please check the "Does this answer your question?" box and mark it as verified.
  • Suggested answer
    Tom_Gioielli Profile Picture
    3,090 Super User 2026 Season 1 on at
    When populating a lookup field in Power Automate, you provide it with the record GUID and the set name of the table it is pointing to. For a Note (annotation) that is linked to a Case (Incident), it would look like this.
     
    Table Set Name for the Case Table: incidents
     
    Example:
    incidents(2fcbcf1a-e35c-4686-80b0-8a74053882b4)
     
    The whole schema vs set name is a tricky one to get right in Power Automate, added to the fact that both tables you are working with have schema/set names that are different than the display names.
     
    If this answer helped, please consider marking as verified.

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 51 Super User 2026 Season 1

#1
Muhammad Shahzad Shafique Profile Picture

Muhammad Shahzad Sh... 51 Most Valuable Professional

#3
Nagaraju_Matta Profile Picture

Nagaraju_Matta 50

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans