Setting Data Level Security for Custom Fields

You can set data level security for custom fields added via VA Custom Fields Wizard.

In order to secure a custom field, you must associate the field with a securable datatype. For example, if you are creating an 'Employee' field that requires security, assign it to the bEmployee datatype.

When creating a custom field, the Wizard provides the option to use a pre-defined datatype. If you do not use a pre-defined type, you must format the field manually. However, if you elect to use a pre-defined type, make sure it is a securable datatype. The following list displays all available securable datatypes:

  • bAPCo

  • bHQCo

  • bLoc

  • bARCo

  • bHRCo

  • bMSCo

  • bCMCo

  • bHRRef

  • bPMCo

  • bCMAcct

  • bINCo

  • bPOCo

  • bContract

  • bJBCo

  • bPRCo

  • bEMCo

  • bJob

bRMCo
  • bEmployee

  • bJCCo

  • bSLCo

  • bGLCo

  • bAPCo

bGLCo

bJCCo

  • bARCo

  • bHQCo

  • bLoc

  • bCMCo

  • bHRCo

  • bMSCo

  • bCMAcct

  • bHRRef

  • bPMCo

  • bContract

  • bINCo

  • bPOCo

  • bEMCo

  • bJBCo

  • bPRCo

  • bEmployee

  • bJob

  • bSLCo

Since data level security requires a 'qualifier' (i.e. company), make sure that the table you are adding the field to contains the appropriate company column. For example, if you are adding a custom field that references the 'bEmployee' datatype, the table must contain the 'PRCo' column. If it does not, you will need to add it before adding any custom field referencing the 'bEmployee' datatype. Adding the 'Co' column to the table makes the table available for selection in VA Data Security Setup.

Once you have set up the user-defined field, access VA Data Security Setup, locate the desired table (Secured Tables tab), check the In Use box, and regenerate the view to incorporate the change. For more information, see VA Data Security Setup.