Support chronological sorting for fiscal month in line/bar graphs when using parameter-driven custom

Surabhi Pradhan-Oracle

Idea Summary
When a parameter-driven custom filter is used to dynamically switch between Fiscal Quarter, Fiscal Month, and Fiscal Week, OAC does not preserve chronological order for Fiscal Month in line and bar graph visualizations if the chart uses a calculated field bound to that parameter. The same calculated field works correctly in a table visualization, but in charts the fiscal months are displayed out of sequence.

This creates inconsistent behavior across visualizations and makes time-series analysis unreliable for users working with fiscal calendars.

Current Behavior
A custom parameter is created to allow users to switch time granularity dynamically. A calculated field is then bound to that parameter and used as the time column.

• In a table visualization, the fiscal month values appear in the correct chronological order.
• In a line/bar graph, the same calculated field does not retain chronological ordering for Fiscal Month.
• The chart appears to ignore the expected ordering logic, resulting in fiscal months being plotted in the wrong sequence.

Expected Behavior
When a calculated field based on a parameterized custom time filter is used in a line or bar graph, OAC should preserve the correct chronological order for fiscal time values, especially for Fiscal Month from the common time dimension.

The sorting behavior should be consistent across:

• tables
• line graphs
• bar graphs
• other visualizations using time on the category axis

Business Impact
This limitation affects dashboards that allow users to dynamically switch between quarter, month, and week views. Since line and bar charts are commonly used for trend analysis, incorrect month ordering can:

• misrepresent time trends
• confuse business users
• reduce trust in dashboard outputs
• require additional modeling or visualization workarounds for a common reporting pattern

This is especially important for customers using fiscal calendars rather than standard calendar months.

Use Case / Replication Scenario

1. Create a parameter to dynamically select Fiscal Quarter, Fiscal Month, or Fiscal Week.
2. Create a calculated field bound to that parameter.
3. Use the calculated field in a table visualization — values appear correctly ordered.
4. Use the same calculated field in a line or bar graph — Fiscal Month values are no longer shown in chronological order.

Requested Enhancement
Add native support for chronological sorting of fiscal time members in charts when the category field is derived from a parameter-driven calculation or custom column selector.

Ideally, OAC should:

• recognize fiscal month as a time-based attribute even when passed through a calculation
• preserve the underlying sort order in chart visualizations
• apply consistent ordering logic across tables and charts without requiring hidden helper columns

Current Workaround
A workaround exists, but it adds complexity:

1. Create a calculation that returns the Fiscal Month Numeric value instead of the display month.
2. Add that numeric calculation to the chart category edge and sort by it.
3. Hide the Fiscal Month Numeric column in the chart.

This workaround is functional, but it is not intuitive and increases implementation effort for report authors.

Why this enhancement matters
This would improve usability for authors building dynamic time filters and reduce the need for manual sorting logic in visualizations. It would also provide a more consistent and predictable charting experience for fiscal calendar reporting.