Better Together T-shirt Design Contest
We're starting a “Better Together” T-shirt design contest. The theme is "Powerful alone. Better together," and we want to see your best T-shirt designs that encompass all 5 products in the family: Microsoft Dynamics 365, Power BI, Power Apps, Power Automate, and Power Virtual Agents. | Read More about T-Shirt Design Contest
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 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
Hello Community Experts,
Suppose I'm providing two different services, service A and service B, i need to collect specific info and checklist all the activities done related to that service, and store it. How would i achieve this requirement
Can you give more details about services, how you can you make difference betwen activities related to service A and service B ?
Thanks for the response Mehdi
I'm not clear about services, but they want specific service to have its related checklists
So that they can mark that checklist related to that service as completed and store it somewhere
This might help you
My idea is this.
1) Create an entity for the service. If you have it, you don't need create it.
2) Create one or several whole number fields for the Service entity to indicate the number of activities.
If all activity types are collected uniformly, create a field.
If each activity type is collected separately, create separate fields for each activity type.
Create a workflow for each activity type. The trigger condition is that this activity record is created. The condition is that if the "Regarding" field of the activity record is service A or service B, the execution is the value of the corresponding whole number field plus 1.
In this way, we can use this number to determine the number of related activities of service A and service B.
Business Applications communities