Considerations for Adding Users in Salesforce Spiff from Multiple Sources

Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience

Available in: Enterprise, Unlimited, and Developer Editions

Available for an additional cost in: Professional Edition with Web Services API Enabled

Adding users from multiple sources into Spiff can lead to significant issues, particularly when different user tables are involved. Ideally, add users from a single source. For example, if you sync users from a Salesforce connector, don’t manually upload the same users separately. Mixing user sources can cause errors, such as unrecognized user.Id or rep.Id, which can indicate conflicting user tables.

Problems occur when you add a user from a secondary source, like a manually uploaded finance user who doesn't have a Salesforce account, and you assign them to a plan. Spiff typically selects the user table with more comprehensive data, like Salesforce. But if Spiff selects the incorrect user table, operational failures can occur.

To prevent such issues, avoid assigning a user from a secondary table to any plans. Otherwise, integrate the user with the primary user table. If errors occur due to multiple user tables, unassign plans from the user in the secondary table and recalculate the data.

Additionally, problems can also occur if you manually upload a user table and then you sync to another user table. Spiff can identify the first table as the primary source incorrectly.

Admin users aren’t added to plans or teams, so syncing them through a connector isn’t required.