Unmask Column Value in Power Pages Basic form

(0) Share

Report

Posted on by NP-17120441-0

We have added column security for Tax ID field in Dataverse table with this change we can see Tax ID column value as ****** in Dataverse table.

We are calling this value using Basic Form in Power Pages. Due to column security authenticated user see Tax ID column value as ******.

What are the setting we need to do for pages Basic Form so authenticated user will be able to see actual Tax ID value as well.

Categories:

Design & build

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

11manish 1,535 on at

Like (1)

Report
Copy link

Link copied!
The issue is not with the Basic Form in Power Pages, but due to Column Security in Microsoft Dataverse.

Since the Tax ID field is secured, users see ****** unless they have proper access.

To fix:

Grant Read permission for the Tax ID field in the Column Security Profile

Ensure the relevant user is assigned to that profile

Verify Table Permissions and Web Roles in Power Pages

If column security does not allow access, the value will always be masked, even if other permissions are correct.

Workaround:

Controlled Access via Role-Based Logic
Remove column security from Tax ID
Control access using:

Table Permissions

Web Roles

Use only if:

Security requirements are not strict

or another workaround:

Custom API / Plugin
How it works:

Create a Custom API or Plugin in Dataverse

Run it with elevated privileges (SYSTEM user)

Retrieve the Tax ID field securely

Return the value only for authorized users

Call this API from Power Pages (via JavaScript or Web API)

This bypasses column masking while maintaining security.

Was this reply helpful? Yes No
NP-17120441-0 31 on at

Like (0)

Report
Copy link

Link copied!

Thanks Manish @11manishfor suggestion .

In our case, any user with access to the Power Page can sign in as an authenticated user using their credentials. As a result, we are unable to apply column-level security profiles for each and every user as they are outside the org setup.

Was this reply helpful? Yes No
NP-17120441-0 31 on at

Like (0)

Report
Copy link

Link copied!

Above response is helpful but in our case, any user with access to the Power Page can sign in as an authenticated user using their credentials. As a result, we are unable to apply column-level security profiles for each and every user as they are outside the org setup.

Was this reply helpful? Yes No
Suggested answer

oliver.rodrigues 9,465 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Can you confirm your Portal version and how the CSP is setup?

I have just tried that and I don't get the same behaviour, basically my Portal user can still see / edit the value.

Was this reply helpful? Yes No
NP-17120441-0 31 on at

Like (0)

Report
Copy link

Link copied!

Did you applied the masking rule? And if yes what setup you did to get the unmasked value

Was this reply helpful? Yes No