In some integration scenarios, users may not want certain ERP fields to be promoted even though they are included in the default mapping logic.<\/p>\n\n\n\n
Some common examples include:<\/p>\n\n\n\n
- \n
- FOB<\/li>\n\n\n\n
- CustomerPONo<\/li>\n\n\n\n
- TermsCode<\/li>\n<\/ul>\n\n\n\n
Since these fields are generated as part of the default payload generation logic, they cannot be removed using standard mapping settings.<\/p>\n\n\n\n
To resolve this, users can configure exclusions using the ERP Configuration object, which dynamically removes these fields from the promotion payload.<\/p>\n\n\n\n
Example Scenario<\/mark><\/strong><\/h2>\n\n\n\n
Object:<\/strong> Sales Order Header<\/p>\n\n\n\n
Suppose you want to exclude fields like FOB or CustomerPONo from the Sales Order Header promotion payload.<\/p>\n\n\n\n
Step-by-Step Solution<\/mark><\/strong><\/h2>\n\n\n\n
Step 1 : <\/strong>Open Developer Console<\/p>\n\n\n\n
Step 2 <\/strong>: Inside the Developer Console:<\/p>\n\n\n\n
- \n
- Click File<\/strong><\/li>\n\n\n\n
- Select Open Resource<\/strong><\/li>\n\n\n\n
- Search for the object: ERP_Configuration__c<\/li>\n<\/ol>\n\n\n\n
![\"Click](\"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-content\/uploads\/2026\/03\/1-Remove-Mappong.png\")
<\/a><\/center>Click on File and Select Open Resource<\/i><\/center><\/font>\n\n\n\n ![\"Select](\"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-content\/uploads\/2026\/03\/2-Remove-mapping.png\")
<\/a><\/center>Select ERP_Configuration__c.obj<\/i><\/center><\/font>\n\n\n\n Step 3 : <\/strong>Run Query<\/p>\n\n\n\n
Execute the following query to review the existing configuration records:<\/p>\n\n\n\n
SELECT Id,
GUMU__Integration_Key__c,
GUMU__Read_Header__c,
GUMU__Read_Payload__c,
Name
FROM GUMU__ERP_Configuration__c<\/p>\n\n\n\n![\"Select](\"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-content\/uploads\/2026\/03\/3-Remove-Mapping.png\")
<\/a><\/center>Select Fields<\/i><\/center><\/font>\n\n\n\n This query helps review the configuration records that control payload behavior.<\/p>\n\n\n\n
Step 4 : Create a New Record<\/strong><\/p>\n\n\n\n
Create a new record in GUMU__ERP_Configuration__c<\/strong> with the following details:<\/p>\n\n\n\n
Name : <\/strong>ExcludeFieldsPromoteSalesOrderHeader100<\/p>\n\n\n\n
Integration Key<\/strong> : Associated<\/p>\n\n\n\n
Read_Payload__c<\/strong> : Add the ERP fields that should be excluded from promotion.<\/p>\n\n\n\n
Example<\/strong><\/p>\n\n\n\n
FOB
CustomerPONo<\/p>\n\n\n\n![\"Excluded](\"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-content\/uploads\/2026\/03\/4-Remove-Mapping.png\")
<\/a><\/center>Excluded Fields<\/i><\/center><\/font>\n\n\n\n Naming Rule for Other Mappings<\/mark><\/strong><\/h2>\n\n\n\n
For other mappings, follow the naming format below:<\/p>\n\n\n\n
ExcludeFieldsPromote(MappingName + ERP)<\/strong><\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
If the mapping name is:<\/p>\n\n\n\n
SalesOrderDetail<\/strong><\/p>\n\n\n\n
And the ERP is Sage 100<\/strong>, the record name should be:<\/p>\n\n\n\n
ExcludeFieldsPromoteSalesOrderDetail100<\/strong><\/p>\n\n\n\n
How It Works<\/mark><\/strong><\/h2>\n\n\n\n
The record created in ERP Configuration<\/strong> stores:<\/p>\n\n\n\n
- \n
- ERP field names<\/li>\n\n\n\n
- Associated Integration Key<\/li>\n<\/ul>\n\n\n\n
During the promotion process, the system performs the following steps:<\/p>\n\n\n\n
- \n
- The promotion logic retrieves records from ERP_Configuration__c<\/strong>.<\/li>\n\n\n\n
- It reads the fields listed in Read_Payload__c<\/strong>.<\/li>\n\n\n\n
- The system checks the generated promotion payload.<\/li>\n\n\n\n
- If an excluded field is found, the system removes the corresponding XML tag<\/strong> from the payload.<\/li>\n<\/ol>\n\n\n\n
Example<\/strong><\/p>\n\n\n\n
Before Exclusion<\/strong><\/p>\n\n\n\n
<TermsCode>NET30<\/TermsCode>
<FOB>Origin<\/FOB>
<CustomerPONo>12345<\/CustomerPONo><\/p>\n\n\n\nAfter Exclusion<\/strong><\/p>\n\n\n\n
<TermsCode>NET30<\/TermsCode><\/p>\n\n\n\n
The excluded fields are automatically removed from the payload.<\/p>\n\n\n\n
Conclusion<\/mark><\/strong><\/h2>\n\n\n\n
After applying this configuration:<\/p>\n\n\n\n
- \n
- The selected fields are removed from the payload.<\/li>\n\n\n\n
- The fields will not be promoted to the ERP system.<\/li>\n\n\n\n
- No changes are required in the existing integration code.<\/li>\n<\/ul>\n\n\n\n
It is important to note that this configuration works only for the Salesforce \u2192 ERP (SF \u2192 ERP) tab<\/strong>. The exclusion applies only when records are promoted from Salesforce to the ERP system.<\/p>\n\n\n\n
This approach allows users to exclude default mapped fields while keeping the integration logic unchanged<\/p>\n\n\n\n
By following the above blog instructions, you will be able to learn \u201cHow to Exclude Default Mapped Fields in GUMU Without Code Changes in SF to ERP tab\u201c<\/strong>. If you still have queries or any related problems, don\u2019t hesitate to contact us at salesforce@greytrix.com<\/a>. More details about our integration product are available on our website<\/a> and Salesforce AppExchange<\/a>.<\/p>\n\n\n\n
We hope you may find this blog resourceful and helpful. However, if you still have concerns and need more help, please contact us at salesforce@greytrix.com<\/a>.<\/p>\n\n\n\n
About Us<\/b><\/br>\n
Greytrix<\/a> \u2013 a globally recognized and one of the oldest Sage Development Partner and a Salesforce Product development partner offers a wide variety of integration products and services to the end users as well as to the Partners and Sage PSG across the globe. We offer Consultation, Configuration, Training and support services in out-of-the-box functionality as well as customizations to incorporate custom business rules and functionalities that require apex code incorporation into the Salesforce platform.
Greytrix has some unique solutions for Cloud CRM such as Salesforce Sage integration<\/a> for Sage X3<\/a>, Sage 100<\/a> and Sage 300 (Sage Accpac)<\/a>. We also offer best-in-class Cloud CRM Salesforce customization and development services<\/a> along with services such as Salesforce Data Migration<\/a>, Integrated App development<\/a>, Custom App development and Technical Support business partners and end users. Salesforce Cloud CRM integration offered by Greytrix works with Lightning web components and supports standard opportunity workflow. Greytrix GUMU™ integration for Sage ERP \u2013 Salesforce is a 5-star rated app listed on Salesforce AppExchange<\/a>.
The GUMU™ Cloud framework by Greytrix forms the backbone of cloud integrations that are managed in real-time for processing and execution of application programs at the click of a button.
For more information on our Salesforce products and services, contact us at salesforce@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"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\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[956,2],"tags":[2995,2991,2989,2997,2992,2987,2529,2990,2999,2996,2993,2994,2588,2988,2998],"class_list":["post-12561","post","type-post","status-publish","format-standard","hentry","category-gumu-features","category-gumu-salesforce","tag-erp-promotion-configuration-salesforce","tag-exclude-fields-from-erp-payload","tag-gumu-erp-configuration-object","tag-gumu-integration-settings","tag-gumu-mapping-configuration","tag-gumu-sage-integration","tag-gumu-salesforce-integration","tag-remove-default-mapping-gumu","tag-sage-erp-integration-best-practices","tag-salesforce-erp-mapping-management","tag-salesforce-erp-payload-customization","tag-salesforce-integration-payload-control","tag-salesforce-sage-100-integration-2","tag-salesforce-to-erp-integration","tag-salesforce-to-erp-promotion-control"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts\/12561","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/comments?post=12561"}],"version-history":[{"count":14,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts\/12561\/revisions"}],"predecessor-version":[{"id":12580,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts\/12561\/revisions\/12580"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/media?parent=12561"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/categories?post=12561"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/tags?post=12561"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- It reads the fields listed in Read_Payload__c<\/strong>.<\/li>\n\n\n\n
- The promotion logic retrieves records from ERP_Configuration__c<\/strong>.<\/li>\n\n\n\n
- Select Open Resource<\/strong><\/li>\n\n\n\n
- Click File<\/strong><\/li>\n\n\n\n