What if in a reflex report the CREFLEX formula created a named range for the resulting data and re-sized/defined it each calculation?

That would let you reference/slice the named range pretty effectively without breaking the formula or relying on offsets. Ie: =INDEX(returnedData,1,)

The function is already re-sizing the range by cell reference so it should be an easy implementation.

-Kieran

Dynamic Dates required on Apps - All apps that meet a purpose should have the functionality to drive the dates within the slicer. We have Financial Reports that should always default to prior month end & Daily Sales Reports that should always open to yesterday...

Folders within "Data" to organise views similar to the Library

Because rowdrill requires contiguous content and does not handle merged cells, a new argument rowDrillEntireRow would insert an entire row at the drill point and copy the entire row when inserting the children.

In mobile reporting we'll often want to cut-down the reported data based on the smaller view port profile. Having an option in CINFO which identifies if a report is being viewed on a mobile device could be used with CREPORTGROUP to manage hiding / rearranging report content.

Add a Query String Editor to Skylights similar to the App Designer where I could add slices, ignore slices and for the big win include a mex statement to dynamically define members. That be Great !

It would be helpful if you have a note at a lower level in an account hierarchy that there was a flag at the higher level (like the comments flag in notes?) that there is a comment below, otherwise you don’t know the comment is there

Typically data sets are oriented to have more rows than columns as it's easier to read. Currently in the cube viewer having the chart take-up the bottom half of the screen means that parts of the data-table are quite often cut-off from view.

This problem would be solved by optionally allowing the splitter to take an vertical orientation, putting the chart on the RHS of screen. Allowing the data-table to extend to the bottom of screen.

In such a mode the default chart would be a horizontal bar type.

The CALUMO icon (top/left) currently does nothing, but could intuitively be a "home button" that refreshes the current page, loading in any Start Page for the user

When I have a large view and I want to PDF it for distribution, I would like to be able to have it Auto-Fit to 1 page like I can in Reports

This would be set on/off at a Datasource/Catalog/Cube level, just like where you wire up the Transactional Drill stored procedures.

Ability to make a report to always open in a new window or tab.

For example when a user opens a report by finding in the library it will always open the report in a new window or tab

When freeze panes are used in the web, and multi line comments are entered. Only the freeze pane with the comments will become multi line, the opposing pane keeps a single row.

Would it be possible to have both freeze pane sides to have the same row height? or alternatively if multi line is done on a freeze pane in the web and its longer than one line make it a ellipse '...' so the multi line effect doesn't affect readability and formatting.

When I add comments to a row it would helpful to be able to add an attachment, like a document or image. An example could be a invoice or some supporting document to demonstrate the validity of the comment.

Default Style CExecStoredProc buttons like Table Editor command buttons.

The default styling of buttons created with the Report Actions wizard are 3d-shadowed and don't fix nicely with the styling of other type of action buttons in the CALUMO interface. ie Table Editors, Dimension Manager.

Users can change the look of these buttons through other features but it would be nice not to have to do that.

The word Browse doesn't have the same meaning as it did in very early versions of CALUMO. The Browse button takes users to the CALUMO Workbench. I know Workbench is not an official name yet, but I think it fits better than browse.

Rather than having to tie it to a database object