How to resolve Dynamics syncing error: Entity 'systemuser' With Id Does Not Exist

Symptom

When syncing records from Dynamics to Outreach that fail to sync due to the error "Entity 'systemuser' With Id Does Not Exist."

Applies To  

Dynamics Admins

Outreach Admins

Why it happens

Outreach doesn’t natively support syncing Owning Teams or Owning Business Units. By default, Owner (systemuser) maps to Owner as a mapped type that looks up to System Users only.

When a Dynamics record is owned by a Team or Business Unit, the lookup isn’t a System User, so Outreach reports that no System User exists with that ID. In practice, this usually means the record is owned by a Team or Business Unit.

Resolution

1. Update the owner of the record in Dynamics to a System User so it can sync natively.
2. If that doesn’t fit the org’s processes, update the default Owner mapping to another System User lookup field, such as Primary Owner.
3. If no such field is available in the CRM today, loop in the account team to discuss further support.

Cause

The error "Entity 'systemuser' With Id Does Not Exist" indicates that Outreach is attempting to locate a user of an associated record but fails to sync because it cannot find the specified user.

Additional Information

How To Map Users or Remove Users Mapping in the CRM Plugin