Masked Text

By Bogdana Botez at Microsoft Development Center Copenhagen

Aliases: Masking out

Context: In the user interface (UI) of a software system, the user enters protected information such as a password, an access key, a credit card number etc.

Problem: The entered information is visible during data entry and whenever any user (the one who entered the data, or a foreign user) opens the UI.


  • Information disclosure: sensitive data is visible in the UI.

Solution: Use the “Masked” field property to display dots instead of characters on the sensitive text field in the UI.

Usage: Figure 1 shows how an unmasked and a masked field look in Dynamics NAV. On page Microsoft Dynamics CRM Connection Setup, the first two fields (Dynamics CRM URL and User Name) are not masked. The next field (Password) is masked. As the user types text into the Password field, the characters are one by one replaced with dots. When the user had finished typing and had left the Password field (moved focus to another page element), then a pre-defined number of dots is showed in the field, no matter what the real length of the password is. This is done so that the length of the text is not disclosed. Hence, no matter if the text had 5, 10 or 20 characters, as soon as the user leaves the masked field, 10 dots will be visible.

Figure 1 - The field “Password” is masked.

To apply this pattern in Dynamics NAV, the developer has two choices:

  1. Mask everywhere

Mask the field in all pages which expose it or will expose it in the future. In this case, masking needs to be set at the table level, by opening the table in design mode and setting the field’s property ExtendedDatatype=Masked.

  1. Mask only in selected pages

Mask the field in only a subset of pages. Open the pages where the field should be masked in design mode, open the property page for the field in question, and set ExtendedDatatype=Masked. This option can be used for example when a field should be hidden from most users (in most usual pages), but still visible to administrators in specific pages.


  • Information protection: sensitive data is stored and can be used by the system, but once entered it is not visible in the UI anymore.


  • “Forgotten password”: the text in a masked field is hidden from all users, including users who theoretically have the right to see it. In this case, if the developer wishes to disclose the text only to certain users, they have to write extra code (like a lookup trigger) which will verify the user’s permissions and if permitted, show or send the clear-text value to the user who requested it.


[1] “Wikipedia,” [Online]. Available:

[2] “GUID Structure,” [Online]. Available:

[3] “Wikipedia,” [Online]. Available:

[4] waldo, “How Do I: Manage Companies in Microsoft Dynamics NAV 2013 R2”.

[5] Microsoft, “Multitenant Deployment Architecture,” Microsoft, [Online]. Available:

[6] B. Botez, “Setup Table design pattern,” Microsoft, 2013. [Online]. Available: [Accessed 31 07 2016].

[7] “Shotgun Surgery,” [Online]. Available: [Accessed 31 07 2016].

[8] M. Fowler, Refactoring: Improving the design of existing code, Addison Wesley, 1999.

[9] “Masking out,” [Online]. Available: [Accessed 29 7 2016].

[10] “Key Vault,” Microsoft, [Online]. Available:

[11] “How to: Configure SSL to Secure the Connection to Microsoft Dynamics NAV Web Client,” Microsoft, [Online]. Available: [Accessed 2 8 2016].

[12] “sniffer,” [Online]. Available: [Accessed 02 08 2016].