Flag entity's attribute as DEPRECATED
407
Views
3
Comments
New
Database

The scenario is an attribute that is decided not be used anymore in an entity, but its deletion is not a good policy at that point.

The only way to "deprecate" is adding a comment in the description, which is not a safe solution because it doesn't prevent developers to keep using it.

So there could be a property in the attribute (called Deprecated) that could grey out the field and warn about its usage in SQLs and other actions.

Very good idea!

I've got some of those attributes in my apps, so such a feature would be quite handy to easily identify another source of technical debt.

On top of your suggestion, those attributes could also be flagged by Architecture Dashboard, so we can find them easily.

Adding to what Ricardo mentioned about Architecture Dashboard, in TrueChange adding a warning when such attributes are used around the application (Aggregates or SQL within that module)