Exceptions for the LoadIfEmpty Named Function

The following are instances where Dayforce can generate an exception when the LoadIfEmpty named function is used in an expression:

• The "Primary" value of the loadingMode parameter is used but the value being evaluated doesn't have an option for default or primary.
  • Example: LoadIfEmpty("<<List_EmployeeMaritalStatus.Item.MaritalStatusId>>","Primary") CONTAINS "9"
  • Exception: Invalid column name 'IsPrimary'.
• The “Current”, “Latest”, or “CurrentAndFuture” value of the loadingMode parameter is used, but the record being evaluated doesn't support effective start or end dates.
  • Example: LoadIfEmpty("<<List_EmployeePayAdjCodeGroupList.Item.PayAdjCodeGroupId>>","Current") CONTAINS "1"
  • Exception: Invalid column name 'EffectiveStart'. Invalid column name 'EffectiveEnd'. Invalid column name 'EffectiveEnd'.
• An invalid list is included in the wfListName parameter.
  • Example: LoadIfEmpty("<<List_EmployeeAdoptionLeaveOfAbsence.Item.FormTemplateId>>","Primary") CONTAINS "1038"
  • Exception: Parameter error in named function LoadIfEmpty - The list List_EmployeeAdoptionLeaveOfAbsence is invalid.
• The wfListName parameter doesn't refer the token correctly.
  • Example: LoadIfEmpty("<<List_UserRoleList>>","AllKeyValues") CONTAINS "1016"
  • Exception: Parameter error in named function LoadIfEmpty - The list List_UserRoleList is missing a token reference. See the Workflow Tokens Guide for the proper format.