Compare two saves

Hi Radek!

Thanks for taking a look at this! I really appreciate it. 

While the PDF format of the auto-documentation would be a lot better than nothing, I've spoken with some folks, and we all agree that a better format would be the .csv or Excel format of the differential deployment function.  This format is usually easier to read, and can be processed by various automated systems - like Discovery Hub itself!

Let me know if you have any other thoughts or questions on this!

Best regards,

Doug Wynkoop

Why not build in a function to check in an xml automatically to github / gitlab?

You can then push any change in xml to git and compare there.

It would also help with version management, i.e. your own versioning. And it would allow reducing the size of the projectRepo database. Delete a project from the database and re-import a certain version from your preferred git solution.

Hello,

I see that this request startet in August 2015 with the thread:

Compare project versions in multiple environments

So I wonder if there is any progress in this. I also need to see the differences between the version I am working with in production environment, and the one that we are about to start to test. Not only as documentation and control of the version, but also to be able to create a test plan according to the changes.

Best regards,

Blanca Hembre

Given the multilevel nature of the datamodel, XML as mentioned by CalmCo makes much more sense than PDF, CSV or Excel. Then the file is an actual treeview of the project. This file would also be useful for many other purposes such as ORM-style access of the project model.

I would however suggest that TimeXtender includes a proper diff viewer and performs the comparison internally rather than pushing it to a git server, to minimize dependencies.

The reason I dislike Radek's suggestion is that we cannot generate documentation (TX crashes, probably due to the size of the project)

Any development with this feature? We have multiple customers asking for this feature.

Thanks for submitting your ideas. Your continued feedback on our product is very important to us.

We will be evaluating your input for future improvements in the product.

At the time of this posting, the current product roadmap is focused on a major evolution in foundational pieces of our software including splitting the development into ODX, MDW, Semantic Layer and User Portal. With this evolution, we will continue to see incredible innovation in the product that may exceed your expectations or make the need for this feature obsolete.

If you have any questions or would like to discuss further, please reach out to me or the dedicated TimeXtender Solution Specialist in you region. Thanks!

Here is my shot a listing changes in TX Objects since a given date or version number.
Based on TX20.5.8.64.
At the end of each record you can find the query to list the history of the object up until the change. 

https://www.dropbox.com/s/sfe9qprd009ljgb/ListChanges.sql?dl=0 

Raf. This is really great and will be useful! Very extensive!
I had something similar but on a much higher level.

Thank you for sharing your work.

Very extensive indeed... This is incredible work Raf! Thank YOU!

I was able to get this to work very easily on v. 20.10.12 as well. Just had to find and delete 3 fields in the select. 

Would you mind if we featured this in a KB article? 

This is fantastic, thank you!  I would love to see this built into a future version, but for now this functionality is stunning.  Really appreciate the very hard work this must have taken to get working. 

@Joseph I would not mind if it is used in a KB article.
Reason for the code sharing is in hopes of having the community or you guys as TX to also add to, improve on or if needed correct it. 

Thanks Raf!!

Excellent work Raf!  Thank YOU for contributing this.  Below is a KB article based on your script:

SQL script to explore version history at object level, to compare two projects or versions