Hello all – another “new user perspective” question / proposal. Would love your feedback.
I fell in love with Quantrix immediately, especially the category linking and natural language formulas.
For my very first formula I wanted to sum over a list of Product 1… items within the “Products” category, putting the answer in another item called “Total”, at the bottom of that item list. To do this I first attempted sum(Products), thinking that this “feels” like how Quantrix should work. But of course this generates a “circular references” error, because Total is in fact part of the Products category. I then tried sum(Product) skip Total, but this doesn’t work (no error) because I guess skip applies to the left side of the formula and so skips the vital job of actually putting the total in that cell…
I know there are multiple ways to accomplish this core basic job in Quantrix. I can sum over a selected range or create a group and sum over the group, and I know I could use sum(summary()). But I keep coming back to the simplest syntax thinking it should work.
Here’s a thought – could the sum([Category]) item always ignore itself but compute over all other items in the category? One would still need to skip subtotals or other items desired to be skipped, but the simple default would just work.
I agree that a simpler syntax initially is more intuitive, and a few more things to consider:
The proposed methodology would need to remove subtotals from the totals just as the current summary function does. In the above Products.Total:Current does not consider (correctly) the total of Group A:Current.
I’m interested in understanding more clearly what you mean by this “One would still need to skip subtotals or other items desired to be skipped, but the simple default would just work.” I’m not sure how you would go about skipping subtotals in the Total.Products as shown above in what you are proposing…
Generally, I agree that sum([category]) would be more like what we are accustomed to using lesser programs, but summary once learned and understood works beautifully, so perhaps a better user materials is really what should be considered. Summary was one of the first things I learned in Quantrix, but that was back when a manual was published…