# See previous states of history, not only the changes made

**URL:** https://community.fibery.io/t/see-previous-states-of-history-not-only-the-changes-made/11318
**Category:** Ideas & Features
**Tags:** history
**Created:** [September 24, 2026, 4:43pm UTC](https://community.fibery.io/t/see-previous-states-of-history-not-only-the-changes-made/11318 "2026-09-24T16:43:19Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)
#### Post date: [September 24, 2026, 4:43pm UTC](https://community.fibery.io/t/see-previous-states-of-history-not-only-the-changes-made/11318/1 "2026-09-24T16:43:19Z")

</div>

There has been a lot of work recently on the historical data of things. (Automations and views activity).

The problem is that this list shows the changes, and you can see details of each change, but it is very difficult to see what the state of the object actually was at any given point in time.

The only place which has this properly is rich text field activity. And this is being merged into the entity activity log, so I hope it will not lose this.

Ideally you can look at any history point for any object and see the full picture of that object in that point in time, as well as an indication of what changed (highlighted) on that change. Then restoring is more clearly restoring that point in time, and not the field changes made in that change.

This is relevant for entities, buttons, automations, validations, views, and anything else which has an “activity” list now.

Another thought:  
Maybe even showing the old fields that existed in that point in time, but not 100% sure about that. IE, if a field existed and the schema changed, still show that field in the entity history as it may help tell the story of the history of this entity. Again, not 100% sure, since “restoring” that entity would then in fact not restore the missing field, so it may be confusing or impossible from a tech standpoint.