You’re offline. This is a read only version of the page.
Announcements
25
I'm trying to create a Dynamics 365 model-driven app for a particular, segregated set of tasks, and I was wondering if it's possible to specify data filters on entities at the model-driven app layer, so that Contacts which have a certain value in a field are displayed within the Contacts section of the app, but any without that value are not sent to the user.
For example, say I have Contacts who can either be Customers or Staff, as determined by a field on the Contact entity, and I want to create a model-driven app around timetable rotas for members of staff. In this app, for a given rota slot, you should be able to specify which member of Staff will be working, but obviously we do not want Customers being specified here! And given that the app is completely unrelated to Customers, it would make sense to never have Customers appear when looking at this entity within this app/only show Contacts with the field set to "Staff". Is this possible?
Views on Tables do not restrict the users from changing the view and then being able to see and link to the wrong Contacts from within the app, so this is unfortunately not a solution.
Security also isn't a solution to this issue, as some users may have access to both this app and other apps where all users should be visible, so they would be able to see and link to all Contacts when they were using the app.
Thanks in advance!
Yes, and I think plugins are slightly overkill for the project this is for anyway. Would be a nice feature to have available for configuration, but then so would many other things which are lacking!
The other thing to consider is to write plugins for retrieve and retrieve multiple to filter out the records you don't need. It is a bit risky as it would bring performance issue to the entire system.
As mentioned in my post, I don't think either of these really satisfies the requirement as I'd like, but I take it that what I'm after isn't possible in Dynamics? In which case I would have to go with the View route.
Hi,
You can create views for Contact entity. The views you create for this particular case, you can apply the filters, and just assign the relevant views to the app.
If you need a further security control, then you can create a new security role and assign the views to that one.
Would that work for you?
regards,
#1
André Arnaud de Cal...
294,081
Super User 2025 Season 1
#2
Martin Dráb
232,860
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
