Setup Steps

1. Navigate to Settings → Database.
2. Click the [all data] button.
3. Select the target environment.
4. Start the sync by clicking the [Start sync] button.

Common Use Case

Your team has finalized a set of updates, including new features, pricing changes, and feature model adjustments, in the development environment. After testing, these updates need to be deployed to the live environment for end-user access.

2. Entity-Specific Sync

This option is more flexible and is designed for targeted data synchronization. It minimizes the risk of overwriting unrelated data and focuses on specific entities.

2.1 Configuration Model Specific Sync

Synchronizes specific configuration models and their associated entities.

Steps

1. Navigate to EMS → Configuration Model Overview.
2. Select the desired configuration model.
3. Click [Sync selected configuration models].
4. Select Related Entities and choose how to sync:
   • Copy: Create new entries in the target environment.
   • Update: Update existing entries or add new ones if they donʼt exist.
5. Select Environment Choose the target environment and confirm.
   

Common Use Case

A product manager has created a new feature model for a product line in the staging environment. The model and its dependencies need to be synchronized to the live environment for sales teams to access.

2.2 Entity Sync

Synchronizes specific database tables (entities) to the target environment.

Steps

1. Select Entity Type:
   1. Common entities are preselected to save time.
   2. Choose the data type to sync (e.g., Features, CRM Accounts, Pricing).
2. Select Related Entities and choose how to sync:
   1. Copy: Create new entries in the target environment.
   2. Update: Update existing entries or add new ones if they donʼt exist.
3. Select Environment: Confirm the target environment and start the sync.

Supported Entities
The following are examples of entities you can sync. Common entities are

preselected; others require manual selection.

Common Entities

• FeatureModel: Includes related data for configuration models.

• Feature: Includes all features and their relations.

Non-Common Entities

These entities are not preselected. Examples include:

• AuditTrail
• CRM Accounts Configurations
• User Roles
• Quotation Templates
• Integration Settings

Common Use Cases

Scenario 1: A department requests updated pricing information for a specific feature or product.

• You can sync just the pricing data to the target environment, ensuring sales teams have the latest prices without syncing unrelated configurations.

Scenario 2: A bug is found in a production feature model, and an updated feature relationship has been corrected in the development environment.

• Sync only the affected feature model and its dependencies to the live environment, minimizing disruption.

3. Sync Logging

After initiating a sync, monitor its progress and diagnose issues using the sync log.

Log Details

• Entity Type: Entities included in the sync.
• From: Source environment.
• To: Target environment.
• Date: Timestamp (e.g., "3 days ago").
• Status: Completed, Failed.
  • Failed actions are marked red.
  • Successful actions are marked blue.

Advanced Diagnostics

Expand logs for detailed execution steps, helping debug failed actions.

4. Database Restore Points

Restore points allow you to revert to a previous state if a sync fails or produces unintended results.

Options

1. Create Restore Point: Takes a snapshot of the database at a specific moment.
2. Upload Restore Point: Upload a .bacpac version of your database to replace the live version. 
3. Restore: Trigger a previously created restore point to revert to that state.

5. Impact of Data Synchronization