Scenarios should stop tracking differences when values return to default

Our organisation is using scenarios to manage alternate model configurations like Peak Day, Average Day, etc. in our main working model. Over time some field values will change from the Base value, and then change back (or the other way around, where the Base is updated to match a scenario). The scenario still tracks this object field as 'changed' even if the value is now aligned with Base - so if Base value is updated later, the scenario won't be. This can be very confusing because even if you go looking for it, as far as I know, there is no easy way to see which objects are being tracked in the scenario (the 'not reported' text in the diff indicates the number, but not what they are).

I think there are some 'quick' improvements that could be made:

• In the scenario manager's diff report, instead of only reporting the number of objects not reported because the current value matches Base, list their IDs and what field(s) they are tracking (or add this as a separate report)

• In the properties panel, if a field is part of the scenario, add a 'revert' button (in the style of the ellipsis button) so it's easy to go back to the Base value. Or at least have a visual indicator on fields to indicate they are part of the scenario.

Longer term I think it would be an big improvement to stop a tracking an object field if it gets set to the same as Base, so that it returns to a fully aligned state.