[arbitrage]

Hello,

I would like to submit a problem about XML import/export in SAI (Synchrnoy Composer 3.4.2-SP2).
We have 3 databases SAI (Development, Test and Production) and we copy the objects SAI of a base to another by export/XML importation.
For each modification of a rule of translation, we create a new version of rule. The object being new, we do not encounter problem at the time of the importation in a new base. On the other hand, we have a problem with the importation of the tables.
If one of the line is different (for instance we have modified a line in the table TOTO in the development base and we import the table TOTO in the test base. So the 2 tables differs by one line), SAI creates a new table whereas we would like that this table be updated.

We are reduced to manually update each modified tables before importing XML files.
Which can lead to human errors.

Does somebody have the same problem?
And if so, how do you circumvent this problem? (I thought of removing the tables of the XML file via tools like XMLSpy but I do not control XML logic).

Thank you by advance.

Michael

[Sandip]

Hello Michael,
If I understand you correctly.

1. You have created objects then created an XML export of it.
2. You import it in Composer.
3. You have modify the objects then created an XML export of it again.
4. When you import in your target Composer, it is getting created rather getting updated.

Am I correct?

Regards

Sandip

[arbitrage]

Hello Sandip!
And thank you for your answer!

You understand correctly except that I encounter the problem (object getting created rather getting updated) only for tables.
It's ok for the other objects.
So I have troubles when I import objects that are link with tables that have been modified.
SAI create a new table rather than update the existing table in the target composer.

Regards.

Michael

[Sandip]

Hello Michael,

I need some Information:

1. Composer Version
2. AccountingIntegrator Enabler version

FYI. This feature is not in Synchrony v4.0 and was planned to be incorported in Synchrony v4.2

Regards

Sandip

[arbitrage]

Hello Sandip,

1. Synchrony Composer is 3.4.2-SP2 Patch2 (and soon SP5).
2. Synchrony AccountingIntegrator Enabler is 1.3.0.1 Patch15.

Thanks

Michaël

[Sandip]

Hello Michael,

This feature is not in Synchrony v4.0 and was planned to be incorported in Synchrony v4.2

Regards,

Sandip