Inbound user BODs: Issues to check

The most common reasons for issues with user BODs that are coming to Landmark from Infor OS Portal (or Infor Ming.le) are shown in the table:

Problem	What to check
Actor is not being created in Landmark.	Review the Sync.SecurityUserMaster BOD to make sure the ActorID property is populated. If the ActorID property is missing, enable Create Users in Draft Mode and make the ActorID property required in Infor OS Portal (or Infor Ming.le).
Actor is not being updated in Landmark.	Make sure that the Infor OS Portal (or Infor Ming.le) attribute IsMingleUser is set to true for the Actor. This attribute is required in order for an Actor to be updated.
ActorRoles is not being updated in Landmark.	Review the Sync.SecurityUserMaster BOD and make sure that roles assigned to the user have the correct Landmark LID.
Error message: Cannot process BOD as Variation ID [#] must be greater than current Variation Id [#]	If you receive this message after attempting to add or delete Landmark user roles, the most likely reason is that a temporary processing mismatch occurred in ION. This is a normal situation that will correct itself. You can ignore the message.