Take the 2-minute tour ×
Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. It's 100% free, no registration required.

Does Tridion (2011 SP1) have an event which can be triggered when we are importing items via SDL Content Porter 2009 SP2? Currently we have a requirement to save release related information. For example: imported release name, imported date and so on.

share|improve this question
    
did you try the rollback feature of the Content Porter where all this information related to previous imports –  Pankaj Gaur Jun 24 at 8:21
    
Thanks Pankaj. we cannot just rollback for some cases.Actually we want to create an audit trail for tracking assets within releases as content gets migrated from a lower source environment to a higher target environment during the content life-cycle. it will create a link between the different versions of the assets across different environments; and ensure that the same version of code and content gets migrated from the source environment to all the subsequent target environments. –  Henry2013 Jun 24 at 9:07

2 Answers 2

up vote 1 down vote accepted

When Content Porter imports an item, it executes a normal save. You can therefore use the standard Save events. In order to distinguish between Content Porter imports and other saves, it might make sense to have a dedicated User for Content Porter imports. Your events can then process Saves by this user accordingly.

share|improve this answer
    
thanks.It make sense we can monitor this event against operating user. now the new problem is where can I get the release related information(release name, version in source system), I need to think about the whole solution to find a mechanism to save those information in somewhere and import event handler can get that information. –  Henry2013 Jun 25 at 7:10

We are using following simple approach.

  • Create component having release info (anyhow you need this info), and include component in you every package.

  • Import date of that component on destination server can full-fill your second requirement.

share|improve this answer
    
Thanks for you suggestion.It is a good solution,however,it seems we need add new field on certain schema which is using by all existing components so that we can add those information into it? for your 2nd suggestion, can you please provide more detail how to find the import date? –  Henry2013 Jun 24 at 9:16
    
When your explore folder you will see modified date in one of the column. Just saw more description in your question, i am using only one component to track the info, but looks like you wanted to have this information in all of the items? is my observation right? –  Raj Kumar Jun 24 at 9:40
    
Yes, we need to trace all the components in one release package in different environment. –  Henry2013 Jun 24 at 10:38

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.