PALO.DATA.SOURCE Identify rule-based values/cells
Function to identify, if a value is calculated or stored in the database.
This enables dynamic reports where a conditional formatting opens cells for data entry ONLY if they are actually stored and not stored and a rule is immediatly overruling the entered value and showing the rule value (e.g. rule = 100, enter 500, cells still Shows 100)3 votes
We are currently working on several features which will allow report formats and styles to be driven by database content.
The fact whether a value is rule-calculated or not will be of the database contents (or states) that we consider for driving such database-based formatting.
It should be possible to get an aggregated total value across dynamic selections from the OLAP server.
Example: get a total revenue value accross selected products matching a certain criteria.
So it should be possible to get an aggregated total of a subset out of a single PALO.DATA formula,
PALO.DATA ("myDB","ProductCube",PALO.SUBSET(<filter/conditions>), ...)
instead of only getting the value for dimension elements via:
PALO.DATA ("myDB","ProductCube","ProductGroupA", ...)8 votes
- Don't see your idea?