Managing Data Loads in Package Tool

Issue

We have discovered that the Package Tool inadvertently creates a new Data Load when an attempt is made to update a single field of an existing one. This behavior can lead to unnecessary duplication of data loads within the system and complicate data management.

Solution

To resolve this issue, the following approach has been implemented:

• When a typedId is provided: The system will search for the existing object in the database and proceed to update it accordingly.

• When a typedId is not provided or the object is not found in the database: The system will seek the existing object using the combination of label, type, and target, and then perform the update.

• In all other cases: A new Data Load will be created.
  This approach ensures data consistency across partitions while preventing duplications.

The handling of Schedules (CS) objects is aligned with this strategy, maintaining their consistency. If a new Data Load is created, the associated schedules are copied, while the original records remain unaffected.

• When schedules is set to null, it indicates that no changes should be made.

• When schedules is an empty array ([]), it signifies that all schedules will be removed.

Importantly, this methodology operates independently of the typedId or calculableTypedId, allowing for more robust management of data loads and ensuring that the system behaves as expected during updates.