Work with Field Security Advanced

Field Security accepts plain text filters and numbers. Furthermore, any filter used on a list in Microsoft Dynamics 365 Business Central is accepted. The only limitation is that filter values must be plain text, i.e. use of variables (like T for today's date), SQL queries and calling methods is not supported.

You can test any filter before configuring the field security on the list itself; e.g. if you want to filter items on the field Type, you manually filter on the value and test whether it works with the values as expect. Any line in the results is authorized to the user.

Syntax Character DescriptionDescriptionExample
Value Equal to the value that is entered.Type the value to find.Smith finds “Smith”.
Value* (asterisk) Starting from the value that is entered.Type the starting value and then an asterisk ().
S finds any string that starts with “S”, Such as “San Francisco”.
*Value* (asterisk) Containing the value that is entered.Type an asterisk, then a value, and then another asterisk.*th* finds any string that contains “th”, such as “Northeast”.
? (question mark) Having one or more unkown characters.Type a question mark at the postion of the unkown character in the value.Sm?th finds “Smith” and “Smyth”.
Value|Value (pipe character) Select multiple values from e.g. an option field, seperated by.Selecting multiple values. Works like Or. The only option when filttering on an option field.InvoiceCredit Memo finds Invoice or Credit Memo

Based upon:

Steps to set up a field security for filtering:

  1. Open an existing field security and click Show more on the header. The fields Filter Field No, Filter Field Caption and Filter Value appear.
  2. Choose a field to filter on in the Filter Field No. field by choosing the AssitEdit button. Select the field in the field list and confirm with OK. Alternatively, you can enter the field id manually if you know it.
    • Note that you can only filter on fields in the same table you wish to set up the field security for.
  3. Enter the filter value in the field Filter Value.
  4. Users need to log out from Dynamics 365 Business Central and log in again for the updated field security to be activated.
  5. The field security is now only active on lines in the table that adhere to the filter.

How to: Allow initial field entry with Field Security

In addition to a complete block modification of fields, field security also has the ability to allow an initial entry and block any modification afterwards. A scenario for this is creation of customers and vendors based upon templates: a user can create a new customer based upon a template by which the fields for posting groups are filled automatically. After creation the fields cannot be modified by users not authorized to do so.

Follow these steps to enable initial field entry for the posting groups in the customer table in an existing field security.

  1. Search for field security in the search field in the top right corner.
  2. Open the existing field security for the customer table.
  3. Open the list Choose Columns by clicking on the column head of the lines and enable Initial Field Entry Allowed.Confirm with OK.- Add the VAT Bus. Posting Group (field no. 110), Customer Posting Group (field no. 21) and Gen. Bus. Posting Group (field no. 88) one by one to the lines from the field list by clicking the AssitEdit button, selecting the field and confirm with OK.Alternatively you can also enter the field no. manually.- Set the value of Initial Field Entry Allowed for every line to TRUE.
  4. Assign permission sets to every line. Keep in mind that the field security is inactive for a user with a permission set not assigned to these three lines. * You can create a data owner using this principle: a user who is able to modify these fields.
  5. Enter a Description on the line, e.g. Use of customer templates.
  6. If not filled yet, fill the field Starting Date. If enabled, the changed field security becomes active after a user logs out and logs in again.

  • complianceapps/3field_security/3work_with_field_security_advanced.txt
  • Last modified: 2020/10/23 11:03
  • by luukvm