Enhance Attribute Capturing on Subject Area Date Columns

Rick195

Part of this idea was implemented in the September release. Modifying the request to address still missing functionality:

1. Enable Subject Area (SA) Date Columns to work natively with time-series calculations (i.e. AGO).
   *This works natively for Dataset dates, but not SA Dates. SA Dates require a manually-built date Dimension with hierarchy in the Semantic Model.
   
2. Provide a capability to implement organization-specific date mappings (i.e. Fiscal Year, Quarter, etc.), that are natively applied to any date fields (like Calendar Year/Month/Quarter/etc.).
   *The workaround for this is also manual date dimension setup for every date field required or custom calculations inside workbooks.

Business value is the same as the original request; reduced development time, more consistent user experience, and additional functionality for Subject Areas to simplify report development in OAC.

===================================

Original Request/Idea:

Request is to enable functionality in OAC to automatically derive date attributes (i.e. YEAR, MONTH, QUARTER) from DATE and TIMESTAMP type values in Subject Areas.

This functionality exists in Datasets and similar objects in OAC, but does NOT work natively against Subject Areas.

If possible, it would be beneficial to also ensure that this functionality also allows for organization-specific date mappings as well (i.e. Fiscal Year, Quarters, etc.)

Business Value:
Reduced development time for Subject Areas.
Consistent user experience building reports in OAC.
Additional functionality available in Subject Areas to simplify report development in OAC.

To replicate this, Subject Area developers have to manually create this logic inside the code for every single DATE type column, which leads to maintenance, additional time in development, and more complexity/less friendliness for users inside the OAC application.

Rick195

We would want the functionality promoted in the March Release to be enabled for Subject Area date values: Use date columns as keys for Custom Knowledge - YouTube

Rajakumar Burra

Agree , it should be extended to SAs as well.

But unfortunately, March update functionality is not usable for now because It is buggy,

• If we add two date columns, in a table, it is not working correctly.
• It is not working for "Use as Filters".