web

You’re offline. This is a read only version of the page.

News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics 365 | Integration, Dataverse... Unable to see custom t...

Microsoft Dynamics 365 | Integration, Dataverse...

Answered

Unable to see custom table Contact Point Consent

(3) Share

Report

Report

Posted on by MandeepT

33

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?

Categories:

Dynamics 365 general

Power Platform integration

I have the same question (1)

All responses Img

All responses (2)

Answers Img

Answers (1)

BJ-20051632-0 117 on at

Like (0)

Report
Copy link

Link copied!

We are trying to build triggers and segments and are also unable to use this table.

Was this reply helpful? Yes No
Verified answer

DAnny3211 11,417 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
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:

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.

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.

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.

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.

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

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

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.

1 people found this reply helpful.

Was this reply helpful? Yes No

Join the conversation

Helpful resources

Quick Links

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

#1

#2

ManoVerse 52 Super User 2026 Season 1

#3

Last 30 days Overall leaderboard

Featured topics

Welcome to the Microsoft Dynamics 365 forum!

Identifying an Org as CDS or Dynamics

Get batch job history log from D365 FO to Power Automate

Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans