- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 06:41 AM
we are moving a huge update set to production this weekend. A team member accidentally deleted an important catalog item. We have removed that from the update set and tried restoring the deleted records but the old RITMs are blank with no variables. I need to make sure these records aren't affected in production when the update set is moved over. Would making a copy of the catalog item in PRODUCTION and renaming it exactly as the original keep us from losing the historical RITM records??
I'm not sure what other options we have an this point but this catalog item is records of employee off-boarding's.
Thank you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 06:50 AM
as long you have removed the DELETE operation from the update set, you should be ok, what I would also do is extract the XML for the catalog item from prod or wherever it exists and use that to import back into DEV.
The DELETE operation has most likely deleted all of the catalog questions/variables when it deleted the item, (cascade delete) hence why your variables are now blank.
main thing is to ensure your delete operation in the update set sys_xml_update records is definitely not in the update set.
you could also export xml of the variables from an existing instance too to ensure you have the variables in case you need to restore them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 06:50 AM
as long you have removed the DELETE operation from the update set, you should be ok, what I would also do is extract the XML for the catalog item from prod or wherever it exists and use that to import back into DEV.
The DELETE operation has most likely deleted all of the catalog questions/variables when it deleted the item, (cascade delete) hence why your variables are now blank.
main thing is to ensure your delete operation in the update set sys_xml_update records is definitely not in the update set.
you could also export xml of the variables from an existing instance too to ensure you have the variables in case you need to restore them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 07:34 AM
Thank you!
Is there anyway to cleanly export the RITMs record with their variables from Production just in case so we can reload the records if needed? I understand how to export the catalog items XML, but what about the 252 records I'm afraid of losing. I will run a mass report on them but I'd like to be able to restore the records in SN if I need to. I just want to make sure I'm thinking of all possibilities.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 08:00 AM
this table contains your item variables: which are linked to the catalog item:
item_option_new
so you can go as usual to your instance url and add /item_option_new_list.do
to export your ritms go to
sc_req_item_list.do
sc_request_list.do
will capture the request and item then:
/question_answer_list.do
/sc_item_variables_task_list.do
capture variables linked to tasks and request items too.
Marc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 08:42 AM
Marc,
Thanks so much for that information. I was able to load the records back into DEV will all your suggestions. So, I know that if we need to we can recover all these items. I guess I will let my member team keep their job! haha
