I’ve got a 2-fer:
*** Describe Feature**
Allow warehouse views to persist hidden columns in input tables.
*** What is the use case?**
There may be columns that we want to use in linked input tables and also persist to the underlying database to use elsewhere. Example is a key value, which the user may not need to know/see or would be confusing, but in another analytic we need it for joining purposes.
*** How often would this feature be used?**
For us, fairly frequently. We’re looking at more and more use cases for input tables and finding lots we could apply this feature to.
*** What is the impact of this feature on your organization?**
Kill Excel.
But seriously, we would like to move a lot of things like account planning and other use cases to all be done in Sigma. Using existing metrics and knowledge of the business from sales leadership to help forecast future sales.
And #2
*** Describe Feature**
Add computed columns to linked input tables. Currently once an input table is created, I don’t have a way (that I can find) to allow a user to make a change to a value there, and have it calculate another column within the table (we can only create more input columns). Currently we have to make a joined table off that original table and it feels like it clutters the information because of duplication. A single table that could be edited and would drive multiple visualizations would really go over well.
*** What is the use case?**
For us we are looking at all sorts of use cases. Other than the one in my first request, we have a number of contractors that we do business with. We frequently have to go through a process of scoring them across a number of different metrics. Some of that does require some input from leadership, basically giving their score. I’d like to pull the relevant KPIs for the contractors, allow leadership to enter their ratings and spit out a scorecard in the end.
*** How often would this feature be used?**
Again, we’ve got more ideas for input tables than time to implement.
*** What is the impact of this feature on your organization?**
No seriously, kill Excel. Finding and reconciling sixteen spreadsheets of the same data but versioned differently by different people is error prone and a waste of time. 95% of the data we need is in the data warehouse. This would streamline and simplify our processes so much.
to indicate their level of interest in developing this request.