/
Data Sync Deprecation with 12.25.0

Data Sync Deprecation with 12.25.0

Why Data Sync deprecation is required?

The three-point data synchronization process involving the Head Office (HO), Web Database (Web DB), and Point of Sale (POS) was deprecated due to several limitations:

  1. Latency Issues: The multi-step sync cycle introduced delays, as each POS had to wait for its scheduled sync window. This lag hindered real-time updates and decision-making.

  2. Error Propagation: The reliance on sequential data transfers (HO → Web DB → POS → Web DB → HO) increased the risk of cascading errors. Any failure in one step impacted the entire cycle.

  3. Scalability Challenges: As the number of POS sites grew, managing sync schedules and ensuring seamless data flow became increasingly complex and resource-intensive.

  4. Modern Alternatives: Real-time APIs and cloud-based solutions emerged as more efficient alternatives, allowing direct, instant communication between systems without intermediate steps.

These factors rendered the data sync process obsolete, prompting a shift toward more agile, scalable, and reliable data management methods.

What advantages are present in Live Sync?

Live Sync represents a significant leap forward in ensuring streamlined and efficient data synchronization. Its real-time capabilities, scalability, and enhanced security make it an essential tool for modern businesses aiming to maintain a competitive edge.

Advantages of Live Sync

  1. Real-Time Data Updates
    Live Sync eliminates the need for manual scheduling or batch data transfers by enabling real-time data updates across all connected systems. This ensures that all stakeholders have access to the most current information at any given moment.

  2. Seamless User Experience
    By providing instant synchronization and doing away with the dependency on Web DB, Live Sync minimizes delays in data availability. This significantly improves operational efficiency and enhances the end-user experience, particularly for dynamic business environments.

  3. Reduced Dependency on Scheduled Syncs
    Unlike Data Sync, which relied on predefined schedules, Live Sync eliminates dependencies on specific time windows for data transmission. This reduces the risk of data latency and ensures a continuous flow of information.

  4. Improved Data Accuracy
    With Live Sync, there is a lower risk of discrepancies caused by delays or missing data packets during scheduled syncs. Real-time updates ensure consistent and accurate information across all systems, improving decision-making and reporting.

  5. Scalability and Flexibility
    The Live Sync architecture is designed to handle higher transaction volumes and can easily adapt to growing business needs. Whether managing multiple POS sites or expanding operations, Live Sync ensures efficient data synchronization without compromising performance.

  6. Simplified Maintenance
    By removing the complexities of managing manual sync schedules and resolving sync errors, Live Sync simplifies the system maintenance process. This reduces IT overhead and allows teams to focus on more strategic initiatives.

  7. Faster Resolution of Issues
    Live Sync provides immediate updates, making it easier to identify and address issues in real-time. This minimizes downtime and enhances overall operational efficiency.

Please note that Web DB is still used for -

  • Customer Information

  • Customer loyalty

  • Item download

What are the current sync scenarios at client side?

Currently clients are having 3 scenarios -

  1. Using only Data sync stores

  2. Using both Live and Data Sync stores (Hybrid sync)

  3. Using only Live sync stores (Ideal Scenario - smooth update to 12.25.0 is expected)

 

Impact in ERP HO version update(12.25.0) for each scenario -

  Sync Mode in HO

  Version Update 12.25.0 Allowed/Not Allowed

  Sync Mode in HO

  Version Update 12.25.0 Allowed/Not Allowed

 Using only Data sync stores

 Not Allowed

 Using both Live and Data sync stores(Hybrid sync)

 Allowed

 Using only Live sync stores

 Allowed

When customer tries to update -

Scenario 1 : Use only Data Sync Store

The following Warning will be shown when a Ginesys user who has only data sync stores tries to update to 12. 25. 0. and they cannot update to this latest version till they migrate at least 1 store to Live Sync and 1 successful round of Live Sync is performed.

image-20241118-135041.png

Scenario 2 : Use both Data Sync & Live Sync Store

image-20241118-135830.png

The above Alert message will come up with detailed explanation of what is going to happen if the user proceeds with the 12.25.0 update.

Post update every time any of the users logs in to the ERP system, the system will show the following alert for 14 days from the date of update.

image-20241118-141441.png

Note - The Remaining days to migrate will keep decreasing till it gets to zero. Then the system will automatically convert the non-migrated stores to Live Sync in the ERP, however the POS end migration will have to be configured by the users.

In case the organization has created but not published some data sync stores before the update, when the user tries to publish the store after updating to 12.25.0 - the following message will show. The user must ensure that the requirements mentioned are strictly provided for.

image-20241118-141030.png

Ginesys recommends - Follow the Data Sync to Live Sync 2.0 Migration to migrate the stores from Data Sync to Live Sync before update.

 

Related content