9 posts tagged with "sync"

---

• [Bug]: Corrected year handling format.

• Resolved an issue where the date used to sync was formatted incorrectly and caused a one-year shift into the future for certain dates at the end of 2023 and 2024.

• The affected dates are:

  • 2023-12-31
  • 2024-12-29
  • 2024-12-30
  • 2024-12-31

• If your sync process runs daily and you're concerned that data was missed from those dates it will be necessary to do a Full Run with the Minimum Date From set to the day before the last date you have missing data from the list above.

  • See Data Source for more information on the Minimum Date From field.
  • See Run Sync for a guide on performing a Full Run.

This version of Sync renamed a field in the data source adapter from filter class to Search Criteria Class.

This will help eliminate confusion between enosix adapter search criteria vs Valence transformation filters.

The enosix team has completed extensive testing to ensure compatibility of the latest enosix apps with the Salesforce Spring ‘25 release. Below are the key details of the testing process and outcomes:

ICU Locale Formats​

You may have received an email or noticed in the Salesforce release notes about the upcoming enforcement of ICU locale formats, which standardize the representation of dates, times, currencies, and numbers across the platform. We want to assure you that this change does not affect enosix components. Our team has thoroughly tested these components with the new formats activated in a Spring Preview org, and they function as expected. Generally, this update does not apply to enosix components.

The email notification you received was triggered by legacy, deprecated surface Visualforce components within your org that utilize API versions below 45. Salesforce requires a minimum API version of 45.0 for all Apex Classes, Apex Triggers, and Visualforce Pages to auto enable ICU locale formats. Consequently, your sandbox org was not enabled on the ICU locale formats due to these outdated API versions.

You can still activate the ICU locale formats with components that use API versions below 45.0.

We are actively addressing these older API version dependencies and plan to update them in the next major release of Surface. This will ensure compatibility with the the latest salesforce releases and prevent future notifications.

For more information on the ICU locale formats and the upcoming changes, please refer to Salesforce's official documentation: Enable ICU Locale Formats (Release Update)

Testing Highlights​

• Regression Testing:

  • A total of 123 regression scenarios were executed to validate functionality and compatibility.

• Products Tested:

  • Sync for Salesforce v1.3.2
  • Surface v2.7
  • SDK v1.6, including the Apex code generator

• Mobile App Compatibility:

  • The Surface app was tested in the latest version of the Salesforce Mobile app.

Testing Scope and Outcomes​

1. Sync for Salesforce v1.3.2:

   • Validated real-time data synchronization between Salesforce and SAP.
   • Ensured consistent performance across core use cases, including object synchronization and data accuracy.

2. Surface v2.7:

   • Confirmed compatibility with Sales, Service and Console apps.
   • Verified Lightning components function in the Salesforce Mobile app.
   • Validated Lightning components work in experience sites.

3. SDK v1.6 + Apex Code Generator:

   • Tested SDK integrations for Transact, including CPQ & Sales Doc.
   • Verified code generation capabilities and deployment to Salesforce Spring ‘25 orgs.

Results​

• Compatibility Confirmed: All tested products are fully compatible with Salesforce Spring ‘25.
• No Critical Issues Identified: Testing revealed no blockers or critical issues.
• Optimized Performance: Minor adjustments have been made to enhance performance and user experience.

The enosix team remains committed to ensuring our solutions deliver seamless integration and superior performance. For any questions or support, please contact our team.

This version of Sync adds a few new features regarding timezones, as well as an updated configuration description.

• We've added support for a configurable SAP Server Timezone Offset, as well as configuring a time for the Minimum Date From:

• We've also updated the configuration settings to provide more clarity about the sync run:

This release contains fixes for the Salesforce Summer '24 Release.

• [Bugfix]: Fixed enosix SAP Source Adapter not being displayed when creating a new link.

This version of Sync adds a couple of new features detailed below:

Source Adapter Table Selection Update​

• Users can now see the CID in the description of the Source Adapter Table.
• When choosing a table from a specific CID, the CID will be automatically populated during the sync.

Limit Record Page Scope​

• Introduced Maximum Page Count and Start Page Count config variables.
• Users can now set a maximum number of records to import for sample-sized testing, especially beneficial in Scratch orgs and Sandboxes.
• Implemented logic to limit sync based on specified page counts, enhancing control over data synchronization processes.

📣 Sync 1.1.2 release has a new feature, Field Length 📣​

NEW Feature: Field Length​

The Field Length displays for source string and decimal-type fields for easier mapping to destination fields with length limits.

• [Feature]: On the Browse Source Scheme, the data type now displays the field length for fields having restrictions on string and decimal data types.
• [Bugfix]: Fixed an exception when a field is mapped that is unrestricted in SAP

1) All SOURCE fields of a record get synced during a Link run​

When you run a Link, all SOURCE fields are synced and displayed within a record of a Sync Event. This feature provides a greater visibility on all SAP SOURCE fields not just the mapped fields.

2) New Adapter Configuration Options​

Additional configuration options are included when configuring the Link’s Source Adapter. To improve performance and filter data at the SAP system-level.

• Prevent unwanted old data being retrieved with the Minimum Date From option
  The Minimum Date From configuration option is used to ensure no date prior to this value is passed in the Date From Field.
• Filter Source Data in SAP with the Filter Class option
  To prevent syncing unwanted data from SAP, the new Filter Class allows you to filter records in a Link. A callable Apex class specifies additional parameters for the enosix Search Context and can be configured to limit the data processed in the SAP system.

3) Constants Filter​

The Constants Filter allows you to add static values to the source fields of a record so they can be used by mapping and other fields.

Follow these steps to configure the constantsFilter in Transformations:

1. Click the include button next to the constants filter
2. Bring the filter on the top, above all Mappings
3. Click the Save Changes button
4. Add a Field Name and Value
5. Click Save Changes

The value assigned to this filter will be displayed in the Source and Destination fields after mapping.

4) Data Type are displayed in the Source Schema​

Data Type are displayed in Transformations to represent fields in the source schema.

• [Feature]: All source fields in search results are passed into the link
• [Feature]: A Filter Class configuration option has been added to allow a link administrator to modify the Search Context, filtering what data is retrieved at the SAP system
• [Feature]: A Constants filter can now be used in links to inject a field with a constant value into the source schema
• [Feature]: Source data is correctly converted into date, boolean, and decimal data types based on the source schema
• [Feature]: A Minimum Date From configuration option has been added to ensure unwanted old data will not be retrieved

Hello All!

📣 enosix is announcing our new solution, enosix Sync for Salesforce 📣

enosix Sync for Salesforce provides a Salesforce native app with the ability to replicate data from SAP to Salesforce.

1️⃣ Data is copied (replicated) from SAP to a Salesforce sObject on a daily or hourly schedule

2️⃣ Synced data can be used in Salesforce Reports, Formula fields since it is copied to Salesforce

Note: Depending on your batch schedule, data may be out of date. For real-time data use our Surface App.

FEATURES:

• Admin friendly interface for configuring synchronization jobs from SAP to Salesforce

• Source date from the library of enosix Sync Rapid Integration Objects

• Target any native or custom Salesforce sObjects

• Built-in data transformation with field to field mapping

• Built in job scheduling

• Built in logging and error reporting

• Syncs can be run in development mode for testing without data updates

• enosix SAP adapter support for:

  • Efficient initial and delta syncing based on last execution date
  • Support for specifying the language used for localized description fields

👉 The enosix Sync app provides the Valence syncing framework and enosix adapter for SAP.

• [Feature]: Added support for sap-language parameter to source localized data from SAP
• [Feature]: Added support for sap-client parameter to source data from the non-default data client in SAP
• [Feature]: Add support for CID to enable specifying which enosix SAP framework calls are invoked
• [Feature]: Add support for scoped paging and batch/page size limits to allow Valence to properly plan the number of scopes needed to efficiently process data
• [Feature]: Add support for specifying a System.Callable for logging HTTP callout information for debugging purposes.
• [Feature]: Add support for specifying Last Queried Date and Initial Load fields to enable enosix SAP framework optimizations to occur for full and partial syncs.