Seth: what about this for adds/deletes. Let us create a working revision, within that track adds and deletes much like within a change order. We can then filter display to hide deletions by default. Then when the revision is ready it flattens it. This could possibly be built on top of the same algorithm as change orders I would think. Track replacements as well and let us see that separate from deletions and roll back. Better yet if a revision can be linked to a location, and adds/deletes in that location are logged to that revision id. Moves between locations should appear much like a delete and an add but an identifier it was a move. That way it can be unmoved or converted into a clone operation. Track adds from clones as such as well - so we can see which item it was cloned from.

Separately a mass update operation log that tracks affected items and previous values. Includes updates from catalog. This could be stored in a separate file even, which only loads the index of operations to memory. Some mechanism to revert the update, report if any affected items are missing or had newer changes to the same fields.

Then a generic basic undo for last actions, like editing a price or margin manually, or converting items to/from accessories, promoting an alternate, moving or cloning, add/delete (including locations).

Seth: That alone would be huge for us. Sometimes you just click the wrong button or delete some stuff you shouldn't or edit the wrong fields.

Seth So today I am working on a project that has (16) different 'solutions' in the project, one of those solutions is in the project (156) times, I noticed 1 of 156 of these solutions, for some reason, wasn't matching the rest. I selected it, right-clicked, update from catalog ->packages. It updated all (156) and not the single one I wanted to update. I know that this is how solutions work, you do want them to be the same, but some price changes in the catalog updated all the solutions and that screwed me.

Here is the issue: I needed all the packages to be locked in price (I hadn't actually locked them yet, my first mistake), I realized my mistake once I saw them all update, but by then it was too late. One click just cost me IDK how long in labor hours because I am not sure where I saved last, nothing else I was working on was price related.

Much sadness and frustration here. Even a single step of undo would have saved me so much time.

Tim Ogilvy: I know this comment is old but wanted to let you know that you can now create Revisions for approved Projects.