CSDT does not honor the <updateddate> field during import
(Doc ID 2878111.1)
Last updated on JUNE 21, 2022
Applies to:
Oracle WebCenter Sites - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
The CSDT import doesn't take the <updateddate>, instead it updates the timestamp when the command was run.Due to this exports need to be created only after first import to get the updateddate.
Else, it causes the import to skip the assets as <updateddate> is older than import date.
Customer's scenario:
- Create package X with Modify 1 to asset A --> Day 1
- Create package Y with Modify 2 to asset A --> Day 2
- 10 days later, import the package to prod instance.
- Day 12, Imports Package X to prod. This is successful and modified date is the import date.
- Then imports Package Y to prod--- Skips the assets as the updated date is newer than updated date in the main.xml
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |