What differentiates "Unique" data loads from "Non-unique" data loads?

The defining characteristic of "Unique" data loads is that they can only have one instance of a record. This means that in a unique data load, each record must have a distinct identifier, such as a unique employee ID or account number, to ensure there are no duplicates in the data. This is crucial for maintaining data integrity and preventing issues that can arise from having multiple entries of the same record within the system.

On the other hand, "Non-unique" data loads allow for multiple instances of the same record. This flexibility can be necessary in scenarios where it is acceptable or necessary to have duplicate entries, such as when recording multiple job titles for the same employee over time.

Understanding the distinction between these types of loads is vital for data integrity in Workday, as it informs how data should be structured and loaded to meet business requirements effectively.