Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 17 Next »

Overview

The Bidirectional Data Synchronization feature enables seamless two-way data exchange between Table Grid Next Generation (TGNG) and an external database. This allows users to maintain up-to-date information across both systems efficiently.

Key Benefits

  • Automatic Data Synchronization: Keep your grid data and database in sync without manual intervention.

  • Customizable Sync Rules: Choose whether database values should overwrite grid values.

  • Improved Data Integrity: Minimize discrepancies by ensuring data consistency.

How It Works

  1. Enable Bidirectional Synchronization in the grid settings.

  2. Configure the Data Source to specify which database table will sync with the grid.

  3. Select Sync Mode:

    • Grid as Primary: Changes in the grid update the database.

    • Database as Primary: Database updates override grid values.

  4. Automatic or Manual Sync: Choose between real-time updates or scheduled batch synchronization.

Flowcharts

  1. Synchronize Bidirectionally Data Mirror (ODBC)

  1. Disconnect Synchronize Bidirectionally Data Mirror (ODBC) → Data Mirror function as normally

Configuration Steps

  1. Navigate to Grid Settings → Data Mirror.

  2. Enable Bidirectional Sync and select the preferred sync mode.

  1. Define Sync Rules:

    • Map grid columns to database fields.

  2. Save Settings and start synchronization.

Common Questions

1. How is it different from the current Data Mirror function?

The current Data Mirror function only allows saving grid data to an external database for viewing purposes.

With Data Mirror Synchronization, you can edit data directly in the external database, and the changes will be reflected in the Grid UI.

2. What databases are supported?

Most major SQL databases (PostgreSQL, MySQL, SQL Server, Oracle.) are supported.

3. What are the limitations?

  • Currently, if data is saved from the Grid UI and later deleted from the external database, it will not be automatically removed from the Grid.

  • Each time you update data in the external database, you must reload the grid in the UI to see the latest changes.

With this feature, users will gain enhanced flexibility in managing data synchronization between Jira and external databases. By ensuring data integrity and providing a configurable source of truth, TGNG aims to streamline workflows and improve efficiency. Future updates will refine and expand upon this functionality based on user feedback and evolving needs.

For further assistance, refer to our Support Portal.

  • No labels