Personalized Community is here!
Quickly customize your community to find the content you seek.
‘Better Together’ Integration forum available
We're launching a how-to forum where you can learn and engage about how Dynamics 365 integrates with other Power Platform products.
Read about Better Together forum
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
In this series of blog posts, I’m looking at the ways to enable an asynchronous conversation between Dynamics/Power Apps users and portals users. The two most common techniques I see use Entity/Web Form Metadata – either the Notes or Timeline metadata option. This post covers the newer way – using the Timeline metadata option.
Enabling Timeline Metadata causes the Portal to display activities related to the record on the Portal. The Portal also comes with a custom activity type, called Portal Comment, can be created by both Portals users and Dynamics 365/Power Apps users.
Unfortunately, Microsoft doesn’t have step-by-step instructions for using the Timeline metadata option.
So here is what I’ve put together:
A few other comments:
If you’re setting up the Timeline metadata on a custom entity, and you just can’t get it to display on the Portal, try changing the Default tab option to something other than Activities, and then change it back.
The Portal code looks at the configuration in the form XML to see if the setting for the Default tab is Activities. When you add the Timeline control to the form, Activities is the default option, and so you see it in the dropdown. My theory is that since it’s the default option, that the value isn’t saved back to the form XML unless a change is made. So to force it to actually save Activities as the Default tab, switch it to something else, save, and then switch it back.
I’d like to acknowledge the individuals who have provided invaluable assistance to this series of posts, including providing their comments, insights, experiences and review:
The post Power Apps Portals: Notes vs Timeline Metadata – Timeline Metadata Deep Dive appeared first on Engineered Code.
Business Applications communities