Retain all information when creating a duplicate (versioning) of an Itinerary
closed
B
Burgundy Salamander
We create versions of a traveller itinerary to enable us to keep the original quote information so we have a record of all previous quote details as changes occur.
What we have found is that when you duplicate an itinerary, the information, traveller details, booking references, contributors, tags and notes are not retained.
We would like to be able to create duplicates of the itinerary with all of the information retained.
Sometimes we duplicate itineraries for the purpose of creating an itinerary for a new customer. In this case the duplicate itinerary features is working as expected and we want this to continue.
Jason Bragg
marked this post as
closed
Thank you for voting on the Retain all information when duplicating an itinerary Canny post.
We are running a discovery process into this request and have identified two distinct use cases that our current 'Duplicate' feature is not fully addressing.
To better understand the different problems we have decided to split this Canny request in two:
- Duplication feature needs more Include/Exclude fields when duplicating
This concept focuses on improving the existing 'Duplicate Itinerary' feature by giving you granular control over which data fields are carried over to the new copy. This approach is primarily aimed at supporting the Iterative Proposal Drafting use case so you can retain Agents/Traveller etc data when duplicating instead of needing to manually add this information later
https://tourwriter.canny.io/feature-requests/p/duplication-feature-needs-more-include-exclude-fields-when-duplicating
- Enable historical versioning of an itinerary
This concept introduces a completely new feature, 'Versioning,' designed explicitly to keep a historical record of an itinerary without cluttering up the database with duplicate records. This would allow users to record the current state of a 'live' itinerary before making changes, ensuring a historical record is retained within the same itinerary.
https://tourwriter.canny.io/feature-requests/p/enable-historical-versioning-of-an-itinerary
Since you voted on the original post we would love your input into the problem that most impacts you. Please click through to either one or both of the links above, add your votes and add a comment with any details you wish to add.
If you have any questions please let me know at jason@tourwriter.com
Jason Bragg
marked this post as
under review
Sina Zimmermann
marked this post as
open
Jason Bragg
Merged in a post:
Carry over client names and notes when duplicating an itinerary
X
Xenacious Kiwi
When a major itinerary revision is required we duplicate so that we can keep the original for reference. The client information should also be duplicated, or the option to keep it or clear it - at the moment it is cleared when an itinerary is duplicated.
Jason Bragg
Hi Xenacious Kiwi To ensure you don't need to send new share settings to your customers (travellers find it less confusing if they dont need to keep track of different links), we recommend when you create a revision itinerary, the new itinerary becomes the reference and the original itinerary is the one you change/update.
We do have plans to enhance the Duplicate feature so you can duplicate with a range of different outcomes. I will merge this post into that request.
R
Right Penguin
It's already requested here :
Tourwriter Support
marked this post as
under review
BTB - have included additional information also to retain agent information.