web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

Unable to see custom table Contact Point Consent

(3) ShareShare
ReportReport
Posted on by 11
Hi everyone,
 
I'm having a weird issue where my users aren't able to see Contact Point Consent (msdynmkt_contactpointconsent4) custom table in PowerApps\Tables. Those affected have the System Customizer security role, and I've inspected the role as well, which has full control over the table. I seem to be the only one in the organization that can see the table, being a System Administrator. For context, this table is related to Customer Insights - Journeys.
 
Has anyone had a similar issue beforehand? Any means to resolve this? 
I have the same question (1)
  • BJ-20051632-0 Profile Picture
    113 on at
    We are trying to build triggers and segments and are also unable to use this table.
  • Verified answer
    DAnny3211 Profile Picture
    11,397 on at

    Hi,

     

    The issue you're experiencing with users not being able to see the Contact Point Consent table (msdynmkt_contactpointconsent) despite having the System Customizer role is likely related to table-level privileges or environment-specific visibility settings.

     

    Here are a few steps to help resolve it:

     

    1. Check Table Permissions: Even though the System Customizer role typically has broad access, verify that the role includes Read access to the specific table in the environment. Sometimes custom tables require explicit permission settings.


    2. Enable Table for All Roles: In Power Platform Admin Center or Power Apps Maker Portal, go to the table settings and ensure that the table is enabled for all roles or explicitly shared with the required roles.


    3. Environment Scope: Confirm that the users are accessing the correct environment. If the table was created in a different environment, it won’t be visible unless they switch to it.


    4. Check App Permissions: If users are accessing the table through a model-driven or canvas app, ensure the app itself includes the table and that the app permissions allow access.


    5. Publish Customizations: After modifying roles or table settings, publish all customizations to ensure changes take effect.


    6. Use Security Role Viewer: Tools like XRMToolBox’s Role Explorer can help you inspect effective permissions across roles and users.



    7.  
     

    Please verify if this helps resolve the visibility issue.

     

    Thanks and best regards,

    Daniele

    Note: This response was prepared with support from Copilot to ensure clarity and completeness.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Martin Dráb Profile Picture

Martin Dráb 45 Most Valuable Professional

#2
iampranjal Profile Picture

iampranjal 36

#3
Satyam Prakash Profile Picture

Satyam Prakash 31

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans