For more information, please refer to this announcement explaining best practices for getting answers to questions.
Offerings load created new records with sysdate as effective start date
Summary:
Reloading the same offerings rows updated the offerings with new effective start date instead of correcting the existing record.
Content (please ensure you mask any confidential information):
We loaded courses and offerings on June 12, 2024, and they were successfully loaded with the correct effective start dates. However, on June 16, 2024, I reloaded the same file, and all the offerings were updated instead of getting corrected.. A new record was added for each offering with an effective start date of June 16, 2024, even though I specified different effective start dates. The old records were end-dated with an effective end date of June 15, 2024. The change event date remains June 12, 2024, for both records in the backend. This is causing issues when trying to