Hello!

Thank you for your question.

 

Catalog items generally store metadata and static attributes related to the data source. They may not support dynamic calculations directly within the attribute fields.
Have you considered using SQL Catalog Item for your Use Case?

Kind regards,
Ekaterina

Thanks ​@ekaterina.ponomareva . Yes, but just thought to have user friendly UI interface easily calculated column can be added or change data type easily. 

Hi ​@akshayl09 , 

Please note that if data type is changed in the source system, then after reprofiling it will also be changed in Catalog Item.

Kind regards,
Ekaterina

Yes, I understand that.

Consider There are different stages of data development raw Layer & Reporting Lyer and there is “ID” column in long Format and same column is presented in Reporting layer in String format as expected data type to avoid any trimming of zero. 

Now I have to create two rules for the same column as it has different data types in different layer of analysis. So, “add attribute” would have help here to create new column by changing data type and tested with same rule instead of creating new rule.

I hope it explained.