Q1: We've added new project fields and syncing from Rocketlane to Salesforce is working, but errors are appearing in the error log when a field has no value. Why is this happening?
A: Errors in the integration error log when a field has no value are typically caused by a mismatch between the field type and/or field values configured in Salesforce and Rocketlane. For example, if a field is set up as a "Yes/No" or "Binary Option" type, both systems must have identical field types and the same allowed values (e.g. "Yes" and "No") configured on each side. If the values don't match exactly, Rocketlane will log an error when attempting the sync.
Q2: How do I resolve the field mismatch errors appearing in the Salesforce integration error log?
A: Check the field configuration in both Salesforce and Rocketlane and ensure the following are consistent across both systems: the field type (e.g. "Yes/No" or "Binary Option") and the allowed values (e.g. "Yes" and "No" must be configured identically). Once the field types and values are aligned on both ends, the errors should stop appearing in the log.
Q3: When a new field sync is set up, does Rocketlane automatically sync the field values for all existing projects?
A: Yes. When a new field sync is configured, Rocketlane will automatically force-sync the field values for all existing projects. This means errors may appear in the log for existing projects if the field is blank or if there is a type/value mismatch, not just for new projects going forward.
Q4: A field is only relevant for certain projects (e.g. based on a specific account type). How can I avoid errors being logged for projects where the field is intentionally left blank?
A: The recommended approach is to ensure the field type and values are correctly configured in both Salesforce and Rocketlane. If the field is genuinely not applicable for certain projects and will always be blank, you may need to review how the integration is set up for those projects to avoid unnecessary sync attempts. Keeping the field configurations consistent between both systems is the key step to preventing errors in the log.