Tag Archives: Salesforce-Sage300C

Effortlessly Import Sync with GUMU’s new “Create Integration Stats” Checkbox in the Entity Mapping Header

In this blog post, we’ll explore a new GUMU enhancement that introduces a “Create Integration Stats” checkbox in the Entity Mapping Header. This feature provides users with the option to manage the generation of records in the Integration_Statistics__c object during the import routine sync. Since these records are generated as part of the sync process,… Read More »

GUMU™ Feature: Auto Update the Last Sync Date field in Entity Mapping/Import after the import routine successfully runs

In this blog post, we’ll walk through a solution that automatically updates the Last Sync Date field in Entity Mapping/Import after the import routine successfully runs. This update is based on the value in the “Update_Last_Sync_by_Days__c” field, which allows users to add a specified number of days to the current sync date and reflect as… Read More »

Optimizing Log Management: Automating Deletion of Logs, Import Job Logs, and Integration Statistics

In a previous blog, we explored how GUMU™ simplifies log management. In this blog, we dive deeper into the enhanced features of automating deletion of log records, exploring practical implementation strategies, and providing insights on maximizing its benefits for the organization. This new functionality will provide users with the ability to delete Import_Jobs__c and Integration_Statistics__c… Read More »

GUMU™ Feature: Experience Quick Product Search on Order Line Items for Salesforce – Sage 300C integration

In this blog, we’ll discuss the new feature, Quick Product Search on Order Line Items in the GUMU™ Integration, designed to streamline the process of retrieving products swiftly during order creation. A QPS or Quick Product Search on order line items enhances efficiency by allowing users to quickly find and select products, speeding up order… Read More »

How to separate Shipping and Billing Street into multiple address lines while importing data from Sage into Salesforce

In this post, we’ll discuss how to split or separate Shipping and Billing Street into multiple address lines in Salesforce. These fields are often used to store address information and are typically set up as long text fields, allowing for multiple lines of data like street numbers, names, apartment or suite numbers, and other details.… Read More »

How to fix the error “Illegal Assignment from String to Decimal” while importing data from Sage to Salesforce

One common issue when integrating SF to any system is the “Illegal Assignment from String to Decimal” error, which occurs when string data from the other system is assigned to a numeric field in Salesforce. Integrating data between Salesforce and ERP (or any other system) can be complex, especially dealing with mismatched data types. This… Read More »

GUMU’s upcoming feature: Enhanced Security Matrix with a Dynamic Tree View!

In this blog we shall outline the new feature enhancement for the Security Matrix UI. The Enhanced Security Matrix provides better access control at both the Administrator and User levels, featuring two distinct components: Security Level Profiles and User Levels. Purpose of Enhanced Security Matrix Previously, accessing different security levels (Profiles and Users) in the… Read More »

How to import data from Sage 300 ERP to Salesforce using the Last Sync field and Last Sync value

In this blog, we will explore how to import data from Sage 300 ERP to Salesforce using the Last Sync Field and Last Sync Value features. GUMU™ for Salesforce is a real-time, bi-directional integration that allows users to sync data between Salesforce and Sage ERP seamlessly. To import data from Sage 300 ERP to Salesforce… Read More »

How to ensure Product Line Descriptions meet character limits while promoting Quotes/Order to Sage 300

A key challenge when integrating Salesforce with Sage is managing Product Line Descriptions meet character limits. Salesforce allows descriptions up to 255 characters, while Sage restricts them to 60 characters, causing truncation and potentially losing important information when promoting quotes or orders in Sage. To prevent this, a validation rule in Salesforce is needed to… Read More »