Hi All, It is high time that GoodData should support Semantic attribute builder and Date output in MAQL. It is one of the biggest lack of feature in GD 1. Derived/Semantic Attribute Builder It would be highly beneficial to have a built-in feature that allows users to define semantic or derived attributes directly within the UI and/or LDM layer. This would improve model flexibility and empower users to create reusable, business-aligned attributes without needing to manipulate source data or hardcode logic repeatedly in MAQL. Like CONCAT, TRIM functions...etc. 2. Enhanced MAQL Support for Data Types (String and Date) Currently, MAQL aggregation functions such as MAX() or MIN() are limited in their support for STRING and DATE data types. In most modern BI tools, functions like MAX(attr_string) return the lexicographically largest string, and MAX(attr_date) returns the latest date, retaining their native data types. We recommend updating MAQL to: Support MAX(), MIN(), and similar functions for STRING and DATE attributes. Ensure that the result type remains STRING or DATE accordingly, allowing downstream formatting and calculations to treat them appropriately. These improvements would bring GoodData more in line with industry standards and significantly enhance its flexibility for advanced analytical use cases.

Thank you for the detailed feedback — these are well-articulated feature requests that align with limitations already documented in the GoodData community. Here's a summary of the current state and what's on the roadmap: 1. Derived / Semantic Attribute Builder This is a known gap. Currently, users who need computed or derived attributes (e.g., using CONCAT, TRIM, or conditional logic) must build these transformations upstream in their data warehouse and expose them as attributes in the LDM. [Community Slack] Good news: This is on GoodData's roadmap. The April 2026 roadmap lists "Computed Attributes" under consideration for GoodData BI: > "We will introduce the ability to create attributes based on metric values, a feature known as bucketing." However, the roadmap description focuses on bucketing (metric-based attribute creation) rather than string manipulation functions like CONCAT or TRIM, so it may not fully address your use case as described. 2. Enhanced MAQL Support for Date and String Data Types This is also a confirmed limitation. As documented: • MAQL metrics always return numeric values — this is a fundamental constraint. [MAQL docs] •

MAX(date)

or

MIN(date)

return an internal numeric representation (e.g.,

2022

instead of a readable date), and date formatting for metric outputs is not currently supported. [Community Slack] • GoodData support has confirmed: "currently the date formatting is not available. You can use metrics like MAX(date) to filter other metrics by date, but at this point they are not meant to be displayed as a formatted date." [Community Slack] The April 2026 roadmap does include "Date Formatting Per Visualization" as an improvement under consideration: > "We will introduce the ability to overwrite the default date format at the column level, enabling charts to use specific formats where needed." This may partially address date display concerns, though it's not the same as returning a native DATE type from a MAQL metric. Current Workarounds Until these features are delivered, the recommended approaches are: 1. Handle transformations upstream in your ETL/SQL layer and expose results as proper date dimensions or string attributes in the LDM — this is the most robust path. [Community Slack] 2. Use

MAX(date)

/

MIN(date)

within WHERE clauses for filtering other metrics, which is the supported pattern. [MAX docs] 3. Use metric formatting to make numeric results more readable, though full

mm/dd/yyyy

date formatting is not supported. Your feedback is well-aligned with existing product requests that GoodData's team is aware of. I'd encourage submitting these formally through GoodData's feedback channels to add weight to the roadmap prioritization. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

Enough of playing with workaround for basic feature like this. Workaround always brings new limitations.

@Krishti Bikal I have submitted this as product feedback. There's not much more I can do from Support point of view. If you wish to escalate this product inquiry, you can do so through your account owner. @Pavel Doubek . Thank you for your understanding.