Sync data

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio Collaboration Services > Accessing Studio Collaboration Services > Management Console Web > Environment >

Sync data

If you have data on your development environment that you wish to preserve in your target environment, you need to perform a Data Synchronization.

This procedure lets you copy data between environments. The data that you can select to be included in the procedure is listed below:

Parameter Values managed in production

Users and their relations

oAreas

oGroups

oLanguages

oLocations

oOrganizations

oPositions

oRoles

oSkills

oTime Zone

oWorking Time Schema

 

You can only import data into an environment for which a metadata counterpart has already been deployed. If you have not deployed an entity into an environment, you cannot synchronize its data into the same environment.

 

MCW_Dev_036

 

note_pin

You cannot import data from a project using a different database engine than the target environment (SQL or Oracle). For example, if your project from where you get the data is SQL, your target environment must be SQL as well.

 

Export data

1. Click the Export file button to open the wizard.

 

MCW_Dev_037

 

2. Select the data of the Parameter entities. From the left, select the data elements that you want to include in the .bdex file; then, click >. Those elements are now visible on the right, which means that they will be included in the .bdex file.

 

MCW_Dev_038

 

3. Move to the User Relations tab. Once again, select in the left panel the user relations you want to export and then click > to make sure they are included in the right group. You can always click the >| button to move all the options available at once.

 

MCW_Dev_039

 

Once you are done selecting the Data and User relations to export, click Next.

In the next step, all the Parameter entities included in the previous step are listed in the left panel (Select entity value). When you click an entity in the left panel, the wizard will show the available attributes for which you can select the Entity key. This key is used in the import procedure to compare the existing records on the target environment against the ones exported from the development environment, to prevent Data Synchronization from creating duplicate records.

 

MCW_Dev_040

 

Select the combination of columns that uniquely identify each record of the entity. Do so for each of the entities listed on the left panel. Once you are done, click Export.

A pop-up alert informs you if the file was successfully generated or if an error occurred. If the file was generated successfully, it is automatically downloaded to your computer.

 

MCW_Dev_041

 

Import data

1. Click Import file to open the wizard.

 

2. Click Browse to display a file explorer. Navigate your file system and select the .bdex file that contains the data you want to import.

 

MCW_Dev_042

 

Mark Override localization for entity values if present on target environment if you need to override existing values.

 

3. Click Open to select the file. Then click Next to move on to the next step of the import procedure.

The second step of the wizard appears.

 

MCW_Dev_043

 

In this step, two lists appear. The one on the right lists all of the data from the selected .bdex file that is going to be imported into the environment. By selecting each element individually you can add or remove data elements from this column to select the objects that you want to include in the import procedure.

Once you have moved the elements between the columns according to your needs, click Next to continue to the last step of the procedure.

 

4. Review if any error message appeared during the validation. Fix or approve the errors and warnings presented before continuing.

 

MCW_Dev_044

 

When you finish reviewing and resolving errors and warnings, click Import to import the data you selected into your environment. If everything runs smoothly, the following message appears.

 

MCW_Dev_045

 

At this point you have finished synchronizing your data from your development environment. You can now use those values and information in the target environment.