Add column calculation type to model insights

Hi Erwin,

I'm curious about the use case behind this, why would you want to see whether a column is a regular or calculated/expression field specifically in Model Insights, rather than checking that in the SF?

From our side: the main goal of Model Insights is to give you enough context to know where to go in the SF, not to duplicate everything the SF already shows.

That said, if this has a clear use case and/or enough upvotes from other developers, we're happy to consider it.

This is especially helpful for us at support where in case of a standstill every second counts, but I can also see other developers benefitting from this. 

When troubleshooting an environment you often have to switch between database, front end, translation and SF. Sometimes you already know the table and column causing the problem (in the gui). So you go to the database to look up the value in the DB, only to find out it is an expression column instead of an actual db column. 

Often the SF is not on the same server as the end production database. Every action not requiring the SF is time won on a standstill. 

I don’t know if conditional layout can be applied to the model insight other wise you could color the column name blue for expression columns to save space. If your philosophy dictates no info that can be acquired from the SF, then would Control not also be irrelevant?
 

Just a different colour would be enough, as it already triggers different thought processes when realizing you are looking at for example an expression field. In several scenarios you can already make conclusions without even going into the SF or even database when you become aware of this.

I would not mind having this marking available in the Model insights already.