{"id":37315,"date":"2024-02-08T16:15:24","date_gmt":"2024-02-08T10:45:24","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=37315"},"modified":"2024-02-08T16:15:24","modified_gmt":"2024-02-08T10:45:24","slug":"power-pages-how-to-track-changes-by-contact-portal-user-in-dataverse-auditing","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2024\/02\/power-pages-how-to-track-changes-by-contact-portal-user-in-dataverse-auditing\/","title":{"rendered":"Power Pages: How to Track Changes by Contact (Portal User) in Dataverse Auditing"},"content":{"rendered":"

Introduction<\/strong><\/h2>\n

Power Pages sites, connected to Dataverse, serve as a powerful tool for modern website development. Dataverse, acting as a versatile database, offers security features, analytics, and automation. However, Dataverse auditing, which logs changes to customer records, initially poses a challenge as it records actions under the application\/system user, rather than the actual contact (portal user) making the changes. The application user will be in the format # Portals-<<site name>><\/strong>. You can see in the screenshot below of Dataverse auditing for application user # Portals-<<site name>><\/strong>.<\/p>\n

\"Dataverse<\/p>\n

Challenges in Tracking Portal Users<\/strong><\/h3>\n

The default setup lacks information about the contact performing operations, leaving organizations in the dark about the user making changes to records in Power Pages sites. The solution lies in a straightforward configuration to associate the portal user using basic form metadata for portals.<\/p>\n

Configuration Steps<\/strong><\/h3>\n

Create Look-ups: Begin by creating look-ups for contacts on the tables being created or modified. If distinguishing between created by and modified by, separate lookups are needed.<\/p>\n

\"Dataverse<\/p>\n

Configure Entity Form Metadata<\/strong><\/h3>\n

Follow these steps to configure basic form metadata for portals:<\/p>\n

    \n
  1. Open the Portal Management app.<\/li>\n
  2. Select the desired form from Entity Forms under the Content section.<\/li>\n
  3. Navigate to Entity Form Metadata.<\/li>\n
  4. Create new metadata.<\/li>\n<\/ol>\n

    \"Dataverse<\/p>\n

    Entity Form Configuration<\/strong><\/h3>\n

    For an Entity Form configured for a table (e.g., Order), create new metadata of type attribute for the lookup attribute<\/strong>. Set the “Set Value On Save” to associate the current portal user as the contactId for the form attribute.<\/p>\n

    \"Dataverse<\/p>\n

    \"Dataverse<\/p>\n

    We have completed the configuration. Now, if someone updates or submits the form on the portal, the value of the portal user\/contact will be audited in Dataverse auditing.<\/p>\n

    \"Dataverse<\/p>\n

    Additional Settings<\/strong><\/h3>\n

    To log the created by contact value, ensure to associate the current portal user on the insert section of the Entity Form\u2019s additional settings tab.<\/p>\n

    \"Dataverse<\/p>\n

    Conclusion<\/strong><\/h2>\n

    In the realm of Microsoft Power Pages and Dataverse, the ability to track changes by Contacts (Portal users) in the auditing process is crucial for comprehensive data management. This blog has provided a step-by-step guide to overcoming the limitations, offering advanced configurations for enhanced user-specific auditing. By implementing these measures, organizations can ensure a transparent digital experience, aligning with the evolving landscape of low-code application development and data governance.<\/p>\n

    Additionally, for a deeper understanding of basic form metadata configuration, you can explore Microsoft’s documentation on Configure basic-form-metadata<\/a>.<\/p>\n

    \"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    Introduction Power Pages sites, connected to Dataverse, serve as a powerful tool for modern website development. Dataverse, acting as a versatile database, offers security features, analytics, and automation. However, Dataverse auditing, which logs changes to customer records, initially poses a challenge as it records actions under the application\/system user, rather than the actual contact (portal\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[2763],"tags":[2743],"class_list":["post-37315","post","type-post","status-publish","format-standard","hentry","category-power-pages","tag-power-pages"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/37315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=37315"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/37315\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=37315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=37315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=37315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}