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 a comparison between the two.
In general, I find that Timeline metadata is my go-to option. It’s the default option on cases in any of the Power Apps Portals templates (Customer Self-service, Employee Self-service, Community and Partner). I like that the author of comment has a real relationship to the record, as opposed to having to rely on a naming convention like is required for notes. I also find users tend to forget about adding the *WEB* to notes to make them appear on the Portal.
Typically, I still see notes being used for implementation that have been around a long time. This includes when Dynamics users are more familiar/comfortable with using notes, or if there are existing integrations that already use notes, and would require re-work to use Portal Comments.
If using the Notes or Timeline Entity/Web Form Metadata doesn’t meet your requirements, another option is to use the subgrid functionality. You can use this technique with Portal Comments, another activity type, or a custom activity/entity. Then you can configure both the subgrid columns, and the Entity Form use to view/edit the records.
I covered this technique as part of this blog post.
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 – Comparison appeared first on Engineered Code.
Business Applications communities