Skip to main content

Notifications

Announcements

🌸 Community Spring Festival 2025 Challenge & Updates🌸
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Merge date fields (Sch...
Customer experience | Sales, Customer Insights,...
Answered

Merge date fields (ScheduledStart/ScheduledEnd/ActualStart/ActualEnd) on ActivityPointer entity

(0) ShareShare
ReportReport
Posted on by Jacob Klein 29
Hello,
 
My team uses ActivityPointer entity to track the activities (phone calls, appointments and tasks). The problem is that ActivityPointer entity has four different date columns: ActualStart/ActualEnd for Phone Calls and ScheduledStart/ScheduledEnd for Appointments and Tasks. It causes issues with filtering and stretches the view in Dynamics, so we would like to merge these fields together, so there is only one field for Start Date and one field for End Date. Optionally, which would be even better, we would like to present ActualStart/ActualEnd fields (for Phone Calls) as ScheduledStart/ScheduledEnd. 
 
I tried to change the mapping of the entity relationship, but this option seems to be systemically disabled. I also tried to run flow that would update ScheduledStart/ScheduledEnd fields with ActualStart/ActualEnd fields whenever Phone Call is created or modified, but I have received an error that ActivityPointer entity can not be updated.
 
Could you please suggest any solution?
  • Jacob Klein Profile Picture
    Jacob Klein 29 on at
    Merge date fields (ScheduledStart/ScheduledEnd/ActualStart/ActualEnd) on ActivityPointer entity
    I didn't think of this solution, but updating the PhoneCall entity really allows to update 'ActivitiyPointer' entity fields in Power Automate.
     
    Thank you for your help. It worked.
  • Verified answer
    Dengliang Li Profile Picture
    Dengliang Li Microsoft Employee on at
    Merge date fields (ScheduledStart/ScheduledEnd/ActualStart/ActualEnd) on ActivityPointer entity
    Hi,
     
    You should update the PhoneCall entity instead of the ActivityPointer entity in your flow.
     
    According to the Microsoft documentation.
    The messages supported by the active pointer entity do not include the update.
    Therefore, you will receive an error.
     
    For the PhoneCall entity, it supports the update in its messages.
     
    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 .
     
    Best Regards,
    Dengliang Li
     

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

News and Announcements

🌸 Community Spring Festival 2025 Challenge & Updates🌸

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Jonas ”Jones” Melgaard – Community Spotlight

We are honored to recognize Jonas "Jones" Melgaard as our April 2025…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 294,255 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 232,984 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans