cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Referencing Phone Call record from custom activity entity

Hello, 

 

I have created a custom activity entity - Call Attempt. I have a ribbon button on the Phone Call entity - when clicked, it creates a call attempt for the user and all these call attempts are shown in a subgrid on the original phone call. I also need to link the original phone call on the call attempt record. So these are the steps that I am following: 

1. User clicks on the Call Attempt button on the ribbon

2. A code runs which creates the call attempt record. 

3. The code takes the text guid of the phone call and sets it on the field in call attempt 

 

I created a power automate flow to run as soon the text guid is populated, then updates the record to populate the phone call lookup field in call attempt. So in the lookup field, I am using the syntax phonecalls(TEXT_GUID_DYNAMICVALUE). 
But I keep getting this error. 

AneeqaPervaiz_0-1612469511503.png

I have tried lots of ways to reference this. /phonecalls/TEXT_GUID. Also hardocded the guid. Used older CDS connector to update record. All to no avail. 

 

Is there another way to reference an OOB activity entity in a custom activity entity?

 

Any help would be appreciated. 

@abm @Pstork1 

 

Thanks. 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hey @abm 

 

Turns out an identifier for activity entities is different. For any custom activity entity, the identifier is ACTIVITY, not the name of the entity like we have for others, eg identifier for phonecall is phonecall, but for any custom activity entity, it is activity. So in my update record, it should have been this;

AneeqaPervaiz_0-1612908303304.png

In my case, I had a boolean field called Call Attempt, and I kept putting that as an identifier - no surprises that I kept getting an error. 

 

Thanks for all your help. 

 

View solution in original post

9 REPLIES 9
abm
Most Valuable Professional
Most Valuable Professional

Hi @AneeqaPervaiz 

 

Try the below

 

image.png

 

In my test I have created a phone call in my flow and next step I used my custom entity lookup set as above.



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

Thanks for the reply @abm 
But it still gives the same error. Please find the screenshot below. 

AneeqaPervaiz_0-1612532677391.png

The boxed field is the one I am trying to update to a link. 

abm
Most Valuable Professional
Most Valuable Professional

Hi @AneeqaPervaiz 

 

Ok what you need to do is try the below List rows filter using activityid. Next step you can map the Phone Call unique identifier (GUID) like I did earlier.

 

image.png



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

I tried it both ways: ActivityID hardcoded, and a dynamic value - both yield the same results. 

AneeqaPervaiz_0-1612534458570.png

 

abm
Most Valuable Professional
Most Valuable Professional

Hi @AneeqaPervaiz 

 

Could you show me your mappings? Have you got any other mappings in that update? Please show a screenshot. Also is that trigger is when a phone call record is updated? In that case you don't need the list. You can get the Id directly from the trigger.

 

Thanks



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

Hey. 

 

So the trigger is when the 'Call Attempt' entity record is created. A button on my phone call ribbon creates a record called Call Attempt. Call Attempt is a custom activity entity - only used with the phone call entity. 

 

So when the call attempt button in phone call is clicked, a call attempt record is created. And on the call attempt record, I need to link the original phone call. So the code which creates the call attempt record also updates a text guid of the phone call from where it was created. 

AneeqaPervaiz_8-1612541938739.png

So what I am having my power automate flow is to run whenever a call attempt is created and a text guid is populated. Then I want the original call attempt (a lookup field to phone calls) to populate with the link via the power automate flow. I have been doing this for another custom button as well where a phone call is created from phone call. That works perfect. 
But referencing the phone call from a call attempt is giving errors. 

AneeqaPervaiz_9-1612541965407.png

AneeqaPervaiz_15-1612542096161.pngAneeqaPervaiz_16-1612542108828.png

 

On my update record step, nothing else is being updated but the lookup link. 

Hey @abm 

 

So the trigger is when the 'Call Attempt' entity record is created. A button on my phone call ribbon creates a record called Call Attempt. Call Attempt is a custom activity entity - only used with the phone call entity. 

 

So when the call attempt button in phone call is clicked, a call attempt record is created. And on the call attempt record, I need to link the original phone call. So the code which creates the call attempt record also updates a text guid of the phone call from where it was created. <image 1>

 

So what I am having my power automate flow is to run whenever a call attempt is created and a text guid is populated. Then I want the original call attempt (a lookup field to phone calls) to populate with the link via the power automate flow. I have been doing this for another custom button as well where a phone call is created from phone call. That works perfect. 
But referencing the phone call from a call attempt is giving errors. <Image 2,3,4>

On my update record step, nothing else is being updated but the lookup link. Image 1.pngImage 2.pngImage 3.pngImage 4.png

Hey @abm 

 

Turns out an identifier for activity entities is different. For any custom activity entity, the identifier is ACTIVITY, not the name of the entity like we have for others, eg identifier for phonecall is phonecall, but for any custom activity entity, it is activity. So in my update record, it should have been this;

AneeqaPervaiz_0-1612908303304.png

In my case, I had a boolean field called Call Attempt, and I kept putting that as an identifier - no surprises that I kept getting an error. 

 

Thanks for all your help. 

 

abm
Most Valuable Professional
Most Valuable Professional

Hi @AneeqaPervaiz 

 

Glad to hear that its sorted now. That naming convention was misleading and of course for the activity entities identifier is always activity. Thanks for letting me know.



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (923)