Enhancement Request: Support Mapping from Multiple Salesforce Objects to a Single Responsive Project
Customer: HPE
Requested Enhancement: Ability to create a Responsive project from a Salesforce Opportunity and populate project fields using data from both the Opportunity object and a related Case object.
Business Requirement
HPE would like to initiate the creation of a Responsive project from a Salesforce Opportunity. As part of that project creation process, HPE needs to populate Responsive project fields using data from two Salesforce objects:
- The Salesforce Opportunity object
- A related Salesforce Case object
This would allow HPE to use existing Salesforce data across related records to automatically populate the Responsive project, reducing manual entry and improving data consistency.
Current Product Behavior
Responsive currently supports a one-to-one object mapping model for Salesforce project creation. This means that project fields can be mapped from a single Salesforce object to a Responsive project.
Because Opportunity and Case are two separate Salesforce objects, Responsive cannot currently map data from both objects directly into a single Responsive project during project creation.
Current Workaround
The recommended workaround is for HPE to bring the required Case data into the Opportunity object first and store it there. Once the necessary Case data exists on the Opportunity record, Responsive can map all required project fields from the Opportunity object to the Responsive project.
Enhancement Request
HPE is requesting the ability for Responsive to support mapping from multiple related Salesforce objects into a single Responsive project during project creation. Specifically, they would like Responsive to create a project from an Opportunity while also allowing project fields to be populated from a related Case record.
Customer Impact
Without this enhancement, HPE must rely on Salesforce-side configuration or automation to copy Case data onto the Opportunity before Responsive can use it. This adds implementation complexity, requires additional Salesforce configuration, and may introduce data maintenance considerations.
Supporting multi-object mapping would allow HPE to streamline project creation, reduce dependency on Salesforce-side workarounds, and improve the overall integration experience.
Current Status
The HPE team understands the current limitation and the proposed workaround. They will review internally and follow up with Responsive after further discussion.
@gosia.rios
@nicole
