Best Of

Working with Objects on a screen (align, mark, moving, rearrange, etc.) in B14 is pretty nice.

Working in a Panel-Object (or combination of Panel in a Tab-Object) and working with several object regarding e.g. marking, moving, aligning, etc. is not as smooth as directly in a screen without a panel.

Is it possible to make for developers working with objects in a panel as easy as working directly on the screen?

ALM (Transporter) shows position information even if we do not change anything of structure of cubes, entity.

This makes customer confused. This is impact for customer to increase checking cost which meta data needs to migrate via ALM.

Could you improve to filter position information?

Currently, the flex grid does not support the visibility of zeros (0) or the display of raised - case IDs 00149013.

Providing this visibility would be highly beneficial for customers, as they rely on this information for reporting purposes. Ensuring that zeros are displayed accurately would enhance data accuracy and improve the usability of the reporting feature.

Many screens have technical selections set by default (e.g: time, version, flags…) that should not be modified ever.

Since the B14 and the change of behavior of Design Mode, we often have screens regressions leading to bugs, due to human errors.

As it is now possible to save the screens selections, we can lose technical ones by mistake

More and more, we need to disable the screen selections option to users because there is a risk to break technical selections. Problem is there is no flexibility at all in navigation

Kindly create a feature to add or remove a dimension from multiple cubes at ones.

It would be nice add a message to involved users when you share a presentation

thanks

Hi all,

We are starting to experiment with RDB cubes, based on the ODBC connector to Snowflake.

One use of these cubes would be to store specific detailed versions of some large cubes (currently cubes more than 30 or 40Gb, soon to reach 50Gb).

However, since RDB cubes cannot have versions, there is no simple way to design reports that would use aggregated versions while keeping the possibility to drill down until the most granular level (level stored in the external SQL table).

Idea: allow MDB versions for RDB cubes.

Benefits :

• Load data directly through a simple "Align" operation, using the ongoing selections
• Single entry point to access the data when building the front-end, allowing easy drill down / drill anywhere without the need for a drill-through setup
• Ability to use the external SQL engine to aggregate the data to load at the expected versions level

It seems that such a thing was possible in past versions, maybe some people will remember ?

Thanks for considering the idea.

Etienne

Make the "Flatten groups level" option available to end users via a dropdown menu to select the starting entity for flattening.