RE: Power Portal with Dynamics 365: Restrict entity records on Portal page
Hi Devon,
Thank you very much for your reply and inputs!
Yes, what you have described is fairly close to the requirement I am examining for the client. In my scenario, it's something like this:
- We have a portal user, who may or may not exist as a corresponding contact record in Dynamics
- In Dynamics, we have thousands of contact records, representing members from various offices. Each office is tracked as an Account record in Dynamics, but currently there is no association between the member contact record and the office account record in Dynamics.
- The portal user represents an office admin. Again, this portal user is not a Dynamics user, and may or may not exist as a contact record in Dynamics.
- Upon login to the portal, what the portal user would like to see is the list of contacts from Dynamics, but only the contacts that belong to the same office as the portal user
I am seeing some challenges trying to achieve the above requirement based on the current setup in the client system. Since there is no association between the contact and account record in Dynamics, and since all contacts in Dynamics are owned by a generic service account user, I couldn't see an easy way how I could configure to filter and only display the contacts from the same office as the login portal user on the portal web page.
I believe your suggestions above would only work if (1) the portal user has a corresponding contact record in Dynamics, and (2) there is lookup relationship on the member contacts in Dynamics to the portal user's contact. I am also not sure if this is something that would be feasible in my scenario since it will involve a mass data update, which won't be easy to do because the client's scenario could involve the same member contact belonging to one or multiple offices.
Do you see any potential solutions (without coding if possible) that I might have overlooked based on the scenario I described above?
Thank you very much!