MxLoader

Good morning, community,

I'm relatively new to using MxLoader and would like to gain a better understanding of how these two functions behave.

From what I gathered in the MxLoader user guide, the "Change" function retrieves the row being sent, searches for it in the database using the key provided for the table, and applies any modifications if changes are detected. On the other hand, the "Sync" function also retrieves and searches for the record, but instead of updating it, the record is deleted and then recreated with a new identifier.

Here's the context of my issue: I've loaded a ZONE table and an OPERATION table, where my operations are associated with a specific zone. When I load data using the "Change" function, I end up with a duplicate row in my OPERATION table (resulting in two identical rows where only the zone differs).

I have a few questions regarding this:

1. What could be causing this duplication of records?
2. What are the potential consequences of deleting a record linked to other tables when using the "Sync" function instead of "Change"?
3. Could this issue be related to the object structure? (Note that all fields used as identification keys are correctly set in MxLoader when I load my data.)

Thank you for your time and insights.

Best regards,

Axel

Hi Axel,

May I ask to which SYNC action are you referring to? In current version of MxLoader there are actions like:

• Query
• AddChange
• Add
• Change
• Delete

What do you mean by SYNC?

Regards!

Good morning, community,

I'm relatively new to using MxLoader and would like to gain a better understanding of how these two functions behave.

From what I gathered in the MxLoader user guide, the "Change" function retrieves the row being sent, searches for it in the database using the key provided for the table, and applies any modifications if changes are detected. On the other hand, the "Sync" function also retrieves and searches for the record, but instead of updating it, the record is deleted and then recreated with a new identifier.

Here's the context of my issue: I've loaded a ZONE table and an OPERATION table, where my operations are associated with a specific zone. When I load data using the "Change" function, I end up with a duplicate row in my OPERATION table (resulting in two identical rows where only the zone differs).

I have a few questions regarding this:

1. What could be causing this duplication of records?
2. What are the potential consequences of deleting a record linked to other tables when using the "Sync" function instead of "Change"?
3. Could this issue be related to the object structure? (Note that all fields used as identification keys are correctly set in MxLoader when I load my data.)

Thank you for your time and insights.

Best regards,

Axel