Currently, any leads created by our marketing system use the integration user's default currency. Instead, we want to have the currency related to the country. There are ways I could do this with custom metadata and a flow but wondering if anyone knows of an out of box solution that can happen in either Eloqua or Salesforce? Since Eloqua is where the leads come from, it makes more sense to me that it's set there but so far google has not shown me any solutions there either. Any advice?
To set the Lead Currency based on the country from where the lead is generated, you can indeed explore options within both Eloqua and Salesforce. Here are some potential approaches:
Eloqua:
- Custom Field Mapping: In Eloqua, you can create a custom field to store the country information of the lead. Then, using Eloqua's integration capabilities, map this custom field to a corresponding field in Salesforce.
- Workflow Rules: You can create workflow rules in Eloqua to trigger actions based on certain conditions, such as the country of the lead. When a lead is created or updated with a country value, you can use a workflow rule to set the currency accordingly.
Salesforce:
- Apex Triggers: In Salesforce, you can write an Apex trigger on the Lead object to automatically update the Currency field based on the Country field. This trigger can run whenever a lead is created or updated and populate the Currency field accordingly.
- Process Builder/Flow: You can use Salesforce's Process Builder or Flow to automate the currency assignment process based on the lead's country. Process Builder allows you to define criteria and actions to perform when those criteria are met, while Flow provides more advanced automation capabilities with custom logic.
- Validation Rules: You can create validation rules in Salesforce to enforce the currency assignment based on the country. This ensures that leads cannot be saved without a valid currency based on the country provided.
Custom Metadata:
As you mentioned, using Custom Metadata in combination with Flow could also be a viable option in Salesforce. You can define currency-country mappings in Custom Metadata and then use a Flow to lookup and set the currency based on the lead's country.
Integration Considerations:
Ensure that your integration between Eloqua and Salesforce is properly configured to sync the necessary lead fields, including the country field and any custom currency fields. This ensures that the currency information is passed from Eloqua to Salesforce accurately.
Evaluation:
Evaluate the pros and cons of each approach based on factors such as complexity, maintainability, and scalability. Choose the solution that best fits your organization's requirements and technical capabilities.
In summary, while there may not be an out-of-the-box solution that directly addresses your specific requirement, you have several options within both Eloqua and Salesforce to achieve the desired outcome through custom configurations, automation, and integration.
Thanks,
A. Gobinath
