When you drop a column or remove a column from your database query, it’s highly possible that your next actions will be in error. Calculated column : if you are using the column in a calculation, you will have a problem there and it’s hard for easymorph to act on this => user must review his calculation.
But there are other actions where it would be possible to automatically adjust and that would be a very cool feature. And you would add more and more actions working like that.
Example : aggregation. I think it’s simple to adapt the aggregation action when a column is dropped, either aggregated or used in the aggregation. Other example : reorder columns. It’s really a pain to modify a reorder action. But in Excel when you drop a column, other columns on the right just adapt and move automatically on the left. Rename action : must be easy to just remove the column from the rename action.
What do you think ? I mean all these corrections must be done by a user but when you have a 100 actions project, you would be so happy that easymorph adapts itself !
And if you don’t want that correction to be automatic, you can propose it in the suggestions only. So user just have a clic to do That works when you add a new column : propose to add it in the aggregation for example. But I think that’s more complex to deal with when a column is added. It’s more easy to do it when columns are removed.