Power Dynamics
  • Power Dynamics
  • 🍕My name
  • D365 CE
    • Copilot
      • 🥐Add Copilot into Rich Text Control
    • Sales
      • Copilot in D365 Sales
      • Export record to PDF
    • Customer Experience
      • Contact Center (Omnichannel)
        • 🐚Internal Live Chat in MDA
        • 📢Add Chat Widget to Power Pages - Proactive Chat
      • Attachment Control
      • Case Routing: Basic Routing rule set
      • Custom SLA for any Entity
      • Customer Insight
        • Journey - Custom Trigger - Call Power Automate
    • Field Service
  • Power Platform
    • Analytics
    • Dataverse
      • Use case for the feature of Record ownership across Business Unit
      • 💡Workaround: Change the OOB "Exchange Rate" of a record
      • Using a Virtual Entity to store historical log (sample)
      • Disable Empty Address record
      • Using Adaptive card
      • Block Unmanaged Customizations
      • 🪃Recycle Bin on Dataverse (Preview)
    • Model Driven App
      • 💡Run SSRS report on MDA mobile
      • 💡Tip: Create a Security Role with "App Opener" minimum privileges
      • Tag @person to notify in MDA
      • Auto search on the Lookup field
      • Activities with multiple related records
      • Embedded Power BI - Dashboard
      • Embedded Power BI - Form
      • "Custom Help" - Is it help?
      • New modern Command Bar
      • Tip: Hide the button "Add Existing Record" on subgrid
      • Custom Page - Why not?
      • Hiding sensitive column data
    • Canvas App
    • Fabric & Power BI
      • New Text slicer
      • Dataverse link to Microsoft Fabric
      • 💡Leveraging Interactive Warehouse Floor Maps in Power BI
      • Calculation Group for Time Intelligence
    • Power Automate
      • ✅Sequential Approval
      • 📤Create an Appointment by Outlook Graph API
      • Dowload SSRS Report and Send email
      • Power Automate: Add a table in Email
      • 💡Tips: Get "DisplayName" of the Lookup field on Power Automate
      • E-sign: Power Automate & DocuSign
  • D365 Finance & Operation
    • General
      • 🇻🇳D365 FnO - Virtual entities: Use case
    • Finance
      • Consolidating Customer & Vendor Balances
    • Supply Chain
      • Landed Cost Series
        • Landed Cost- Essential Configuration
        • Landed Cost Scenarios 1
Powered by GitBook
On this page
  • Using data masking rule
  • How to show after hiding...

Was this helpful?

  1. Power Platform
  2. Model Driven App

Hiding sensitive column data

#PowerPlatfor, #MDA, #D365

PreviousCustom Page - Why not?NextCanvas App

Last updated 1 year ago

Was this helpful?

Hello guys,

Have you got the requirement on how to hide the sensitive column data when implementing the Power Platform or D365 CE for the client?

Hiding or showing sensitive columns is very useful and necessary. It helps protect information and prevents unauthorized access to sensitive data.

Today, we will talk about some ways you can hide sensitive columns.

Using data masking rule

Data masking rules provide a robust method to secure sensitive information in Power Platform or D365 CE, such as IDs, credit card numbers, and personal information,... Implementing these rules ensures that this type of data appears in a concealed format, safeguarding it from unauthorized viewing.

My case: The client asked me to hide the Phone Number (format: Vietnam) on entity Contact.

  1. Enable column security for the column you need to mask. In my case, I enable the column Mobilephone on the Contact entity.

  2. Create "Secured masking rule": Create this component in the Solution.

  • Name: The name of the masking rule.

  • Description: An optional description of the masking rule.

  • Regular expression: A regular expression to identify the data to be masked. Define Regex rule in C# is designed to mask Vietnam phone numbers as below.

// I used the sample Regex from this GitHub : 
Regex = ^(0|84)(2(0[3-9]|1[0-6|8|9]|2[0-2|5-9]|3[2-9]|4[0-9]|5[1|2|4-9]|6[0-3|9]|7[0-7]|8[0-9]|9[0-4|6|7|9])|3[2-9]|5[5|6|8|9]|7[0|6-9]|8[0-6|8|9]|9[0-4|6-9])([0-9]{7})$

Run testing firstly:

  1. Create "Attribute Masking Rule": Create this component in the Solution.

  • Entity: Apply a masking rule to the table. My case is the "Contact" entity

  • Attribute: The column applied the masking rule of the Entity. My case is the "Mobiphone" column of the Contact entity

  • Masking Rule: select the specific making rule that has been created in Step 2

That's finished the configuration. Now, we run testing. If you input a valid Vietnam Phone number -> This value will be masked after saving.

How to show after hiding...

  • By utilizing the Field Security Profile alone, without the Masking Rule, managing access becomes more straightforward. You can rapidly adjust user permissions by adding or removing users from the field security profile.

  • However, the Masking Rule operates on the uppermost layer, overriding the functionality of the Field Security Profile. This feature effectively bypasses the Field Security Profile mechanisms.

So How to do that ???

You imagine that you just hide this information for some users and the remaining can see it. So...

See you again in the next section. Thank you and hoping well. [NTD]yns.Asia ... Thank you.

😇
🫶
☕
❤️
invite me a cup.
3 steps to configure
Enable column security
Create "Secured masking rule"
Masked Test Data - Vietnam Phone Number
Apply masking rule for entity & column
Test Mask Phone Number on the Contact record.
Drawing
Page cover image