We require LOCAL SUBJECT AREAS to not DROP renamed columns if ALIAS is maintained

Adrian Nedelcu-Oracle

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

GSO / GBF

Description :

In cases where we make column name changes in Presentation while keeping Alias, Local Subject Areas function differently than Workbooks.

Specifically in the case of a name change, but alias maintained, the Workbook and all visualizations, calculations and objects referencing the changed column will function normally.

In the case of an LSA, if the LSA is edited and saved, even with no changes performed, the column which underwent a name change will be dropped, affecting all downstream objects (DATAFLOW, DATASETS, WORKBOOKS)

Use Case and Business Need :

This has a significant impact to all DV Developers in any scenario when a name change occurs. Recently due a LOB name change we had more than 300 local subject areas impacted, and over 100 developers requiring action to be taken with full list of objects impact closing on a thousand.

This is occurring on CORE Oracle DV Production Instance, with over 2000 Monthly Active Developers and a total of more than 11000 monthly active users.

More Details

Full details on how this issue is generated including ADMINISTRATION TOOL edits can be seen in video below. SSO login required

https://otube.oracle.com/media/DV+Developer+Column+Name+Change/1_r35enhwl/236129023