Transferring data between identical metadata objects of the 1C database through the substitution of UIDs in the SQL database

If it becomes necessary to migrate from one supplier configuration to another, or when updating a modified configuration, if the Supplier later added an object that was added by us independently, it may turn out that the old and new objects have different internal identifiers. When comparing / merging configurations, it can be seen that the old document does not match the new one, since they have different internal metadata identifiers, and when loading (updating) a new provider configuration, the old document is deleted along with all the entered documents.

There are several options for solving this problem:

A. Transferring deleted documents after updating the configuration to a new metadata object using exchange rules (this method recommends using 1C);

B. Using customization rules for comparison / merging of configurations. In this case, you can configure the correspondence between the old and new metadata object. The old object (with the old UID) will remain in the user base, and during comparison / merging it will be modified by changes to the new provider object. But at the same time, the object will remain with the old UID and will not stand up for support.

B. Start using the new provider configuration object by transferring all the data from the old object to it by replacing UIDs. In this case, the configuration can be put on support, use automatic updating, and besides, there is no need to carry out data transfer as such. The risk of receiving incomplete data transfer, broken links, etc. is eliminated. With this technique, the data does not change at all.

Let us examine option "B" in detail.

1. , , . , ( ..) . . , , , «» . . , «» ( , ), — :
   
   
   
   
   
   
2. / , , . , . : , , — . , , .
   
   
   
   
3. XML-, :
   
   
   
   
   
   
   
   
4. «» (ivi_.xml), :
   
   :
   
   
   
   :
   
   
   
   :
   
   
   
   
   
   
5. «” .
   
   
   
   
6. , :
   
   
   
   
   
   
7. , ,, .
   
   https://its.1c.ru/db/metod8dev/content/1798/hdoc — .
   
   Params, 1 MS SQL. , Deflate:
   
   
   
   
8. Params DBNames:
   
   
   
   SQL Management studio HEX, , . HEX BIN. HEX to BIN. https://tomeko.net/online_tools/hex_to_file.php?lang=en
   
   , , 955126 .
   
   
   
   
9. . : https://infostart.ru/public/618906/
   
   DBNames ( — 1, — SQL):
   
   
   
   
   
   
10. – 1 , SQL.
    
    .
    
    
    
    
11. (Inflate) , (9)
    
    
    
    
12. SQL- DBNames:
    
    UPDATE [ukf_real_test].[dbo].[Params] SET [BinaryData] = (
    
    SELECT *
    
    FROM OPENROWSET(BULK N'C:\DBNames-FM.dfl', SINGLE_BLOB) tt) where [FileName] = 'DBNames'.
    
    , 1 :
    
    UPDATE [ukf_real_test].[dbo].[Params] SET [DataSize] = 954234 where [FileName] = 'DBNames';
    
    
    
    
13. 1. , 1 . , .
    
    
    
    
14. 1 .
    
    „“ „“:
    
    
    
    .
    
    1 , .
    
    , , , .
    
    

. , , — .