How to Exclude Default Mapped Fields in GUMU Without Code Changes in SF to ERP tab
Summary
This explains how to exclude default mapped ERP fields like FOB or CustomerPONo from promotion payloads in Salesforce to ERP integration using GUMU, without changing any code. It uses a configuration object in Salesforce to dynamically remove unwanted fields during data promotion, making it easier to customize integration behavior. Salesforce teams can apply this approach to keep default code intact while controlling field-level payload content through declarative configuration. The solution is specific to the Salesforce → ERP direction and leverages query and record creation steps in the ERP Configuration object.
Takeaways
- Configure ERP_Configuration__c records to exclude default mapped fields from promotion payloads.
- Use naming conventions like ExcludeFieldsPromote(MappingName+ERP) for exclusion records.
- Excluded fields are removed by deleting corresponding XML tags from the ERP payload.
- This method avoids any code changes in the underlying GUMU integration logic.
- The exclusion applies only to Salesforce to ERP (SF → ERP) promotions.
In some GUMU integration scenarios, certain fields are mapped by default within the integration code. Because these mappings are defined at the code level, users cannot remove or deactivate them directly from the Mapping UI. Even if a user attempts to delete or disable the mapping, it may still remain active because it is embedded in the promotion logic. However, there is a simple configuration-based workaround that allows users to exclude these fields during promotion without making any code changes. In this blog, we will explain how default mapped fields can be excluded from the promotion payload using the ERP Configuration object. Problem In some integration scenarios, users may not want certain ERP fields to be promoted even though they are included in the default mapping logic. Some common examples include: FOB CustomerPONo TermsCode Since these fields are generated as part of the default payload generation logic, they cannot be removed using standard mapping settings.