I will update this thread as soon as i have a ETA for the bug fix. Thanks Avinash

Hello, Thanks for the feedback. I can reproduce this bug in Sep 2024 OAC update and i have opened a bug for the PD team. I will follow up on the fix.

Hello, Thank you for the feedback. I have reported this as a bug and will continue to follow up. Thanks Avinash

@Abhinav Chaurasia-Oracle FYI - good enhancement to the CF framework.

A bug has been logged for the engineering team to increase the current value limits. Thanks Avinash

We have delivered this functionality - in viewer mode, as a end user you should be able to move/re-order columns and remove columns on table and pivot tables. Thanks Avinash

@Rajakumar Burra The status change was done by a colleague by mistake. Accept our apologies. Our goal as a collective team is to help our customers. I do not have a workaround for your use case. I have engaged with engineering teams for workaround to increase limits on current value - like i said, this limit is enforced as…

Hello, Possible values limit is increased to 10,000. Initial values is still limited to 1000 - and this was to safeguard the workbook performance at initial load when executing parameter values. It looks like the current value of parameter is also limited to 1000 (again as a guardrail for performance). I will discuss with…

Hello, This is an active project in development currently scheduled for a 1H CY2025 release target. Thanks, Avinash

Hi Michal, Any code change that deals with the data model of the viz / affects the grain of the query is a very complex change. Author's need can be broken down into three categories: Obtain values from columns related to the displayed result set but not part of it. These will include: Sort based on a column that is not…

Hello, This feature is in active development and target release is still 1H CY 2025. Once we complete our integration testing, we will be able to share a release target in early 2025. Thanks, Avinash

Parameter values that are bound to the workbook filter (parameters are workbook scope). This is the current behavior and subject to change. Product team recommends to: use Workbook filters primarily for authors to define the scope of the data on the workbook/canvas and hide the filters or make them as read only (using the…

This feature is currently in development. Target release early 2025.

@sridhar vijayakumar OAC May 2024 has a new feature to bind a parameter to the exclude mode of the filter. See this video for details: https://www.youtube.com/watch?v=OaC6-9jmGEs&list=PL6gBNP-Fr8KU55dSbzkEKySjSDWlL3BWm&index=2

Yes, this is planned. We need to get this prioritized.

@Jorge Olmeda can you confirm you are on OAS 2024? We added label support for primary & secondary measures on Tile and parameter support with OAC May 2023. So if you are on OAS 2024, you should see the Label in the Measure tab and also use the @parameter reference.

Thank you for the clarity - we will track this as a issue and provide a fix.

We support Precent as a format option - are you referring to any other feature. Thanks Avinash

@alekya-kilaru - in your example YTD and PTD are columns in your datasource?

Gabby is right. I did not pay attention to the screenshot showing workbook filters Personalization is supported on the dashboard filters and viz filters. Please read this blog for details: https://blogs.oracle.com/analytics/post/enabling-end-user-personalization-in-oac-workbooks