When should a dimensional function be used in a report's Query calculation?

Question

Options

• Awhen the data source is a dimensional or dimensionally-modeled data source
• Bto allow relative date functions to be performed against a non-dimensional data source
• Cto convert a non-dimensional data source into a dimensionally-modeled data source
• Dto allow drill up and down on a non-dimensional data source

• A
  7% (5)
• B
  75% (50)
• C
  13% (9)
• D
  4% (3)

Explanation

A dimensional function in a report's Query calculation exists specifically to enable relative date operations (like "last 30 days" or "year-to-date") against data sources that are not natively dimensional - making B correct. Option A is backwards: dimensional data sources already support these functions natively and don't require this workaround. Option C is incorrect because the function doesn't actually convert the underlying data source's structure; it merely wraps the query to unlock dimensional behavior at report time. Option D is wrong because drill up/down is a navigation feature tied to the data model itself, not something a query-level function can grant.

Memory tip: Think of the dimensional function as a compatibility shim - you only need a shim when something doesn't fit natively. If the source were already dimensional, no shim needed.

No community discussion yet for this question.