Purpose:
The purpose of this article is to provide information to Outreach users regarding Outreach's Unmanaged Salesforce Package.
For more information about the Salesforce Unmanaged Package process, refer to the Last Touch Sequence Attribution (Unmanaged Package) Guide article.
Q: My organization previously set up some or all of the Engagement Panel fields; does this replace those fields?
A: If you had set up some or all of these fields in the past, you will find that this package has created duplicate fields. Feel free to delete all fields that have API names that start with outreach_ on the Lead and Contact object except for Current Sequence Name (outreach_current_sequence_name) and Finished Sequence (outreach_finished_sequences). These fields are used as part of the Process Builder flows. If your organization has already mapped these two fields in Outreach to a legacy custom field you will need to modify your mappings to point to the Outreach data to these newly created fields.
Q: What are the names of the process builders? Can I modify them?
A: Since this is an unmanaged package you have complete access to the processes that power this functionality. You can find these in the Process Builder with the following naming:
- Outreach - Update Last Touch Field (No Contact Role)
- Outreach - Update Last Touch +Finished Sequence Fields
- Outreach - Update Initial Sequence - Leads
- Outreach - Update Initial Sequence - Contacts
- Outreach Fill/Update Date Added to Sequence -- (for Contacts)
- Outreach Fill/Update Date Added to Sequence -- (for Leads)
Q: Can I adjust the Revenue by Sequence Salesforce report?
A: Yes, the report is standard opportunity report type and is intended to serve as a starting point for your organization.
Q: Why isn't my Salesforce report showing data?
A: This only works for opportunities created going forward and is not retroactive. To see data show up on the report, refer to the Test the Activity of Revenue & Pipeline Correlation Reports process of the Last Touch Sequence Attribution (Unmanaged Package) Guide. The out-of-the-box report uses the standard Amount field on the opportunity. If your business uses a different field to track revenue, you will need to adjust the filters and columns on the report to reflect that.
Q: Why don't I see any data in the Current Sequence Name field on my Lead/Contact records?
A: If you have just finished mapping the fields for the first time, it may take Outreach some time to completely sync the data to Salesforce. To test with a single record, navigate to a prospect record in Outreach that is active in sequence and force sync the Lead. If you do not see the data populate on that record in Salesforce, check the field mappings in Outreach. Refer to the Map Outreach Engagement Fields to Corresponding Salesforce Fields section of the Last Touch Sequence Attribution (Unmanaged Package) Guide to confirm correct mapping.
Q: What are the field names and values for my Salesforce instance for Leads and Contacts?
A: Refer to the table below:
| Field Name | API Name | Object | Field Type |
|---|---|---|---|
| Actively Being Sequenced | outreach_actively_being_sequenced_c | Contact | Checkbox |
| Current Sequence Id | outreach_current_sequence_ID_c | Contact | Text |
| Current Sequence Name | outreach_current_sequence_name_c | Contact | Text |
| Current Sequence Status | outreach_current_sequence_status_c | Contact | Text Area |
| Current Sequence User Role | outreach_current_sequence_users_role_c | Contact | Formula |
| Current Sequence Step Number | outreach_current_sequence_step_number_c | Contact | Number |
| Current Sequence Step Type | outreach_current_sequence_step_type_c | Contact | Text |
| Current Sequence Task Due Date | outreach_current_sequence_task_due_date_c | Contact | Date |
| Current Sequence User SFDC ID | outreach_current_sequence_user_ID_c | Contact | Lookup (user) |
| Finished Sequences | outreach_finished_sequences_c | Contact | Text |
| Initial Sequence Date | outreach_initial_sequence_date_c | Contact | Date |
| Initial Sequence ID | outreach_initial_sequence_id_c | Contact | Text |
| Initial Sequence Name | outreach_initial_sequence_name_c | Contact | Text |
| Actively being sequenced | outreach_actively_being_sequenced_c | Lead | Checkbox |
| Current Sequence ID | outreach_current_sequence_id_c | Lead | Text |
| Current Sequence Name | outreach_current_sequence_name_c | Lead | Text |
| Current Sequence Status | outreach_current_sequence_status_c | Lead | Text Area |
| Current Sequence Step Number | outreach_current_sequence_step_number_c | Lead | Number |
| Current Sequence Step Type | outreach_current_sequence_step_type_c | Lead | Text |
| Current Sequence Task Due Date | outreach_current_sequence_task_due_date_c | Lead | Date/Time |
| Current Sequence User SFDC ID | outreach_current_sequence_user_id_c | Lead | Lookup (user) |
| Finished Sequences | outreach_finished_sequences_c | Lead | Text |
| Initial Sequence Date | outreach_initial_sequence_date_c | Lead | Date |
| Initial Sequence ID | outreach_initial_sequence_id_c | Lead | Text |
| Initial Sequence Name | outreach_initial_sequence_name_c | Lead | Text |
| Attributed Finished Sequences | outreach_attributed_finished_sequences_c | Opportunity | Text |
| Last Touch Contact | outreach_last_touch_contact_c | Opportunity | Lookup (Contact) |
| Last Touch Sequence | outreach_last_touch_sequence_c | Opportunity | Text |
Q: I just added the new Current Sequence fields but I do not see them available in my Field Mappings in Outreach; where are they?
A: If these fields were just recently added, you may need to refresh Outreach to get them to display. For more information regarding missing fields in Salesforce, refer to the Troubleshooting Missing Salesforce Fields in Outreach Plugin article.
Q: What should I do if I cannot enable the Change Dashboard Colors?
A: Refer to the Salesforce A system administrator cannot enable 'Change Dashboard Colors' article.
Additional Resources:
Last Touch Sequence Attribution (Unmanaged Package) Guide
Troubleshooting Missing Salesforce Fields in Outreach Plugin
© 2019 Outreach.io
Comments
0 comments
Article is closed for comments.