Transferring data with the "reference" type To transfer an object of the "reference" type, you must make sure that all reference catalogs have been created in the consuming system. Otherwise, the object will be created incorrectly or the stream will return an error. Our connectors check whether the system contract is met (completeness, correctness). Only when all conditions are met will the message be sent to the consumer Building an object from multiple tables Object information can be stored in multiple sources.
You need to request data from each source and merge it before sending. Our solution lets you aggregate object data. For example, you can collect "orders" and "payments" separately from different sources and pass them as "orders with payments." Deleting a row from an object's tabular section means that row is not registered for 1C exchange. The receiving system must know this 1C behavior and calculate changes on its own. Our connectors can check for deletions in the tabular section. If a deletion occurred, they mark it in the storage.
Consumers do not need to perform calculations.