Unifier (MOSC)

MOSC Banner

Suggestion: Retain Column Aliases from Custom Data Models in UDRs (Unifier 25.10+)

edited Sep 9, 2026 5:54PM in Unifier (MOSC)

Following a recent Support Request, we discovered that Unifier version 25.10 contained the following change:

"

Integration: New REST APIs

User-Defined Reports: The UDR REST Service V2 provides a well-structured JSON output with appropriate element names instead of generic column identifiers. It also removes user-specific number formatting to ensure consistency across consuming applications.

"

This is an extremely disruptive change for several reasons. The actual behavior that exists is as follows (determined through testing, confirmed by Oracle SR):

  • If the Column Alias used in the SELECT statement of a custom Data View matches the Data Element Name of any Data Element in the tenant, the UDR will force the Column Heading in the UDR to be set to the matching Data Element
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center