Merge snapshots

Hi,

Can anyone tell me in which version of Create the ‘merge snapshot’ functionality was first introduced ?

(Libby can’t tell me!)

Thanks,

Mark

Hi @markgpearson ,

The Merge Snapshot functionality was first introduced all the way back in Create v10.3, which was released in Summer 2019.

Hope this helps :slight_smile:

1 Like

Thanks for the reply, Ali. We’re testing this at the moment and one thing we’ve come up against is the level of tagging available in the merge snapshot. For example, I am developing a page and have made x3 changes: dev1, dev2, dev3. I’m then asked to fix a bug on the same page, fix1. How do I then exclude my development changes from the merge ? Looks like it is not possible: I’d have to include all changes for the page in my merge snapshot. There are workarounds I guess e.g. take a copy of the dev page, rewind the original page to a pre-dev stage and then do the fix. But that is not very user-friendly.

Do you have any suggestions as to how this might work ?

How about allowing page elements to be tagged ?

Thanks,

Mark

Hi @markgpearson ,

It’s a very good point you’ve made here. The thing with merge snapshots is that you’re analysing and merging components, not each historical change per component.

So in your example, a page has 3 changes identified, you’re not choosing which change to merge for that page, rather the page is what is being merged (with all of its changes) - Hope this makes sense.

That said, the workaround you’ve suggested is an idea to use for your process.
Me personally, I ensure my latest changes are published, then I revert back to the history to review and find what changes have been made before reverting back to my “latest” state of play.

You could probably raise an Idea in the Community ideas, though, for us to review this for future improvements.

Hope this helps :slight_smile:

Thanks. I’ll raise an Idea.

Idea #1702119 Add tags to component elements and fields