Skip to Content
Oct 03, 2019 at 09:09 PM

Do I really need other these nodes in calculation views?


Knowing that SQLScript provides a lot more possibilities when modeling (window functions, statistics function etc) and also Table Functions can now be used as datasources (well for a while now :) ).

My questions then :

1. Are there any technical benefits of modeling in graphical calculation views besides ease (i.e drag and drop)?

2. Are there any demerits to adopting a model as below for example?

table —> Table function (SQLScript) —> Calculation view —> SAC/BO

why would I need these other nodes (join, union, excepts) if I can achieve the same via SQL!!! There must be something

Are there any documentation / References or blogs or best practices?