Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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
we're having problems with PSA due to the fact that we have not only the root business unit, but also 2 sub BUs. It seems that actuals are always created in the root business unit (owner is 'SYSTEM')
So project managers from one of the sub BUs would need global read privileges on the actuals entity to see the actuals related to their projects. But that would make it possible for them to see every single actual in the entire org, which is something that is legally not allowed.
Now my idea was to have a workflow trigger on actual creation, and then assign that actual to a user/team from that business unit based on the contracting unit. The workflow is easy to create and works, however I do not know whether PSA cares about who the owner of an actual is. I'm concerned that some Microsoft plugin or something might fail if I take away actual ownership from 'SYSTEM'.
Also, is performance an issue if you have a workflow triggering on actual creation (since there's so many actuals being created)?
Thank you very much.
Thomas Schick I'd see a red flag with using real-time workflows for this. I've not tried this but if you do PoC this, I'd first try Flow for this as it doesn't affect CE's performance. Rupa Mantravadi, adding you to the topic for insight into pros and cons of changing Actual ownership in multi-BU scenarios.I propose a doc on Actual ownership based on scenarios. In some cases the owner is a user and in others, system.
it's an async workflow, not a real-time-workflow.
I would love to read a doc on this topic. For right now, however, I just need to know if changing actuals ownership is supported by the system at all, or if it's just something you can technically do, but should not do because it breaks the system in some way. Can you or your colleague provide me that answer?
Pushing this topic in the hopes of a reply.
There is no good solution to this. PSA was designed ignoring BUs.
You might consider designing a custom entity that holds a copy of actuals. And records for that custom entity could be owned by various users. You could only expose that custom entity in your app while hiding actuals from navigation and securing all fields on actuals using Field-level security. It would be quite cumbersome to implement and may require not only workflows but also plugins but if you have a legal requirement you could do it.
For some other sensitive records you could also mconsider team-ownership but not for actuals.
We can only hope that this will get re-designed by Microsoft to become aligned with normal CE security.
Business Applications communities