Tagged with calculation - Visokio Forums http://forums.visokio.com/discussions/tagged/calculation/feed.rss Mon, 30 Oct 17 14:38:02 -0400 Tagged with calculation - Visokio Forums en-CA Keyboard shortcuts: skip re-calculate all (2.8+) http://forums.visokio.com/discussion/1962/keyboard-shortcuts-skip-re-calculate-all-2.8- Fri, 21 Dec 2012 11:39:06 -0500 Alfonso 1962@/discussions
In these models, the user has to interact frequently with the User Interface, changing variables and inserting values on grids or dataView. As the performance sometimes isn't enough fast to drive it with automatic calculi he has to disable and enable re-calculation of the formulas and refresh the calculi. However, currently access to this functionality from the menu is not 'user friendly':

Data>Formula>Calulate automatically. (enable/disable automatic calculi).
Data>Formula>Recalculate all (CTRL+SHIFT + R) (force all calculi).

My suggestion is to give this enable/disable or 'skip' functionality a Keyboard shortcut combination such as as (CRTL+ SHIFT +S ) for saving a file, for example.

This way, the user can select between two modes, either act and wait for all the calculi process with the time involved, using shortcut like (CTRL+SHIFT+R) , or wait only a few time to see the results of his action. We need it but I think is will also be useful for other people and projects.]]>
Calculational precedence: At the risk of being boring... http://forums.visokio.com/discussion/437/calculational-precedence-at-the-risk-of-being-boring... Tue, 05 Oct 2010 18:24:35 -0400 Guy_Cuthbert 437@/discussions
I understand why this happens, but I wanted to raise it as an issue again - because it prevents usage as shown in the attached image; how does the user know which (if either!) summary is correct?!

The areas of the image to focus on are the "Stock Turn" and "Stock Payback" columns; these are calculated columns - the formulae are:
  • Stock Turn = Sold Qty / Current Stock Units (i.e. how many times, in a year, could I have sold the current stock given the sales rate over the past 12 months?)
  • Stock Payback = Current Stock Cost / Gross Profit (i.e. how many years does it take to generate a Gross Profit equal to the current value of stock?)

The Pivot in the top left shows the number of items in a given Product Range - when selected, we have 2 Tables (top right, and bottom) which show a breakdown:
  • Top Right = full details i.e. every Item in the selected Range (77 items in the image)
  • Bottom = summarised by Product Group and Supplier, so that we can see whether we can discuss stock issues (longevity or excess value) with specific Suppliers

The aggregation in the bottom table uses "Formula result" to calculate the [correct] values for each Supplier / Product Group. But in the Table view there is no way of using "Formula result" to derive a result... so we get different values in the two tables for the same underlying data.

Omniscope does provide the option to "Calculate formula field results for group result values" (from the Formula menu, in the Table view), but whilst this yields the correct answer in the Top Right table, it doesn't affect the bottom table... and has the undesirable side effect of forcing all fields required by the formula to be displayed in the table (which, for complex multi-field formulae, isn't an option).

I will post the result of selecting "Calculate formula field results for group result values" in a follow-up post (I can't add 2 images to this entry) to illustrate the problem.

I appreciate that Grouping in tables is an architectural problem... but it means that it can be very dangerous to using multiple Table views on the same page; it's easy to confuse the user. More fundamental is that Omniscope is not presenting the *right* number in some cases; or at least it is very easy for the user to make that accusation, with some justification. Many people are used to reviewing summaries in tables - and they remain a useful way to look up a specific value - but such discrepancies in values present real problems when delivering client solutions.

One for discussion, I think...]]>