10.12.2018, 17:11 | #1 |
Участник
|
crmtipoftheday: Tip #1207: Check applied entity permissions in portals
Источник: https://crmtipoftheday.com/1207/chec...ns-in-portals/
============== Liquid is a great templating language adding flexibility to your Dynamics 365 Portal templates. However, as any abstraction, it hides some of the things happening under the hood, including some security filtering. Consider this fragment running on authenticated page: {% fetchxml my_contacts %} {% endfetchxml %}Record count: {{ my_contacts.results.total_record_count }} And… the count is 2 while expected to be the total number of contacts in this sample environment (around 20 or so) . Er? This is because the portal engine applies entity permissions to all constructs retrieving the data including fetchxml. To see where did the things go wrong (or right – depending whether it’s your point of view or of your system administrator), use xml property of the fetchxml object. That will tell you what’s actually being executed. {{ my_contacts.xml | escape }} In my case resulting fetchxml looks like this highlighted lines (injected by the portal engine) explain why I’m seeing only two records (my portal is based on Customer Service):
Источник: https://crmtipoftheday.com/1207/chec...ns-in-portals/
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору. |
|
|
|