Q: Can Rocketlane's native Salesforce (SF) integration be modified to sync data from plain text fields in SF to user fields in Rocketlane?
A: Yes, it is feasible to modify the native Salesforce (SF) to Rocketlane (RL) integration to sync data from plain text fields in SF to user fields in Rocketlane. If your team members have limited Salesforce licenses and cannot be directly mapped via Salesforce user fields, you can store their email addresses in a plain text field in Salesforce. Rocketlane can then be configured to bi-directionally sync this text field with a "Single User" field in Rocketlane, effectively mapping the user based on their email.
Q: Why would I need to sync a Salesforce text field with a Rocketlane "Single User" field?
A: This approach is particularly useful in scenarios where:
- Your internal teams, such as the Services team, have limited access or licenses for Salesforce.
- You still need to sync user-specific details (like an 'Integration Consultant') between Salesforce and Rocketlane.
- By using a plain text field to store the user's email in Salesforce, you can maintain the bi-directional sync without requiring every relevant team member to have a Salesforce license.
Q: Why can't I create a new Rocketlane project by re-toggling the "Push to Rocketlane" field on the same Salesforce object, and how can I do it?
A: Rocketlane's integration with Salesforce is designed to link only one Rocketlane project to a single Salesforce object at a time to ensure seamless field synchronization. If you try to re-toggle the "Push to Rocketlane" field on a Salesforce object that's already associated with an existing Rocketlane project, it won't create a new project.
To create a new Rocketlane project from a Salesforce object that has already been used, you must first unlink the existing Rocketlane project from that specific Salesforce object. Once the previous link is removed, you can then re-trigger the project creation process from Salesforce, and a new Rocketlane project will be generated.