Forum

Hello.

We have to store some catalogs, charts of accounts, charts of calculation types in text templates in XML format, because in predefined values we can only store code and description, but we need more attributes and tabular sections.

And now i found out that when we delete all lines from tabular section in XML then after loading this XML to information base old lines still exist in tabular section.

I tested this on Chart of calculation types in 8.3.3.721 and 8.2.19.68.

The code for reading XML is quite simple:

Object = XDTOSerializer.ReadXML(XMLR)

Maybe it happens because XDTOSerializer work with XDTOfactory, which contains XDTOpackage with your xml file schema, and it take tabular sections from this schema?

I use the global XDTOSerializer object to serialize and deserialize in one configuration without using any reference to XDTO Packages.

It seems that it takes the tabular section from database.

I don't understand how could the tabular section of deserialized object contain any data which doesn't exist in XML?

Maybe I explained the problem not very good.

For example, i have an XML with serialized ChartOfCalculationTypesObject without data in tabular section. Then I deserialize it and write to database. Now I have the chart of calculation types object in database without records in tabular section. Then i manualy add one line in database. Then  I deserialize original XML one more time and write it to database. Now I have the chart of calculation types object in database with one record in tabular section.

With catalog is the same thing

Could you provide a configuration and XML files with serialized objects?

I made a test configuration with one catalog and XML file inside it as a template.

Thank you for the information. I sent it to our developers.

Hello, Mikhail.

This problem is found even in 8.1 version and can not be a problem with migration to 8.3. It will be fixed in future versions, of course.

You should definitely hire us as beta testers.  

In 8.3.4.365 issue still exists

Hello. This problem still exists. (I tried on 8.3.4.482)

Hello!

I'm sorry, but this issue is still in progress. Thank you for keeping your eye on it.