{"id":4104,"date":"2018-09-06T08:57:42","date_gmt":"2018-09-06T07:57:42","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=4104"},"modified":"2022-08-23T15:24:25","modified_gmt":"2022-08-23T14:24:25","slug":"can-i-keep-an-items-change-history-when-exporting","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/can-i-keep-an-items-change-history-when-exporting\/","title":{"rendered":"Can I keep an item’s change history when exporting?"},"content":{"rendered":"

Can I keep an item’s change history when exporting?<\/strong><\/h2>\n

The simple answer is yes!<\/p>\n

I certain scenario\u2019s you may need to export items from one Cradle database and import them into another. Depending on your reasons for this, you may want to retain an items change history. However, this is only possible when using the Standard Cradle Export Format<\/em> and Change History<\/em> is enabled for your item types.<\/p>\n

Enabling Change History<\/strong><\/h3>\n

Each item type<\/em> can have change history<\/em> enabled in the Project Schema<\/em> via the Project Setup<\/em> dialog. You can see how to enable change history<\/em> in this Cradle help article.<\/a> Once enabled you should start to receive a change dialog pop-up when making changes to items of that type.<\/p>\n

\"Image
Change details<\/figcaption><\/figure>\n

You can choose to enter a change comment<\/em>, which can include your reasons for making this change. This can prove useful in situations where there are a large number of users in one database enabling full traceability.<\/p>\n

Standard Cradle format<\/strong><\/h3>\n

Cradle export format files are unique to Cradle and can store every piece of PDB (Project Database) information which does include an item’s change history<\/em>. However, the type of information that is stored can be further defined by you in the export interface.<\/p>\n

\"Image
Export dialog<\/figcaption><\/figure>\n

 <\/p>\n