is it possible to export a guided tour with all of the steps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2019 05:48 AM
I tried an XML export of the tour record, then an export of all of the steps. But on import it fails to run and won't open in Designer. Is there an easier way to get a tour from the Test environment into our Production environment?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2019 08:10 AM
You need to export the xml's from the below tables
1. sys_embedded_tour_guide (this is the parent table)
2. sys_embedded_tour_step (navigate to the list with query condition as Guide = Tour name) (this is the child table)
The import them in the target system. First import parent table, then import child table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2019 09:19 AM
Yes, that is what I tried. I think something must be different in the target system. It is New York, while the origin was London. The tour shows up but only gets to the first step.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2019 05:28 AM
Hello Will, I ran into this same issue (however I am in Madrid)...If you look at each of your steps, under the Tour Steps tab, are there values in the Target Reference field? If not, you will need to export the Guided Tour elements that were created when you built the tour. The elements are located in the sys_embedded_tour_element table. For my issue, I added the Created by column and filtered on my ID, performed the export to XML and then imported the file into our test environment. I went into each Tour step and the target reference field was populated and the tour ran as expected.
I hope this helps!
Jeremy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 10:05 AM
Yes, my team discovered that 3 is the magic number in terms of tables to export from and then import into another instance. It is extremely helpful if you can sort by a field such as 'created by' to narrow the scope of your export as needed.
1. sys_embedded_tour_guide
2. sys_embedded_tour_step
3. sys_embedded_tour_element
In our case, we needed to export from one Utah instance to another Utah instance.