True or False: The ${derived_table_or_view_name.SQL_TABLE_NAME} syntax is not supported with a datagroup's sql_trigger parameter.

True or False: The ${derived_table_or_view_name.SQL_TABLE_NAME} syntax is not supported with a datagroup's sql_trigger parameter.

• A. True
• B. False
• C. Only in certain contexts
• D. Only for derived tables

Answer: (A)

The statement is true because the ${derived_table_or_view_name.SQL_TABLE_NAME} syntax, which is used to reference the underlying SQL table or view name of a derived table, is indeed not supported in the context of a datagroup's sql_trigger parameter. Datagroups are designed to manage data freshness and caching by tracking when data is updated. They typically rely on simpler SQL expressions or raw table names rather than the dynamic references that are used with derived tables. Since the sql_trigger parameter requires a specific and static reference, using a syntax that pulls in dynamic context does not work in this scenario. This reinforces the need to understand the limitations of using derived table specifics when setting up datagroups in LookML.

The statement is true because the ${derived_table_or_view_name.SQL_TABLE_NAME} syntax, which is used to reference the underlying SQL table or view name of a derived table, is indeed not supported in the context of a datagroup's sql_trigger parameter. Datagroups are designed to manage data freshness and caching by tracking when data is updated. They typically rely on simpler SQL expressions or raw table names rather than the dynamic references that are used with derived tables. Since the sql_trigger parameter requires a specific and static reference, using a syntax that pulls in dynamic context does not work in this scenario. This reinforces the need to understand the limitations of using derived table specifics when setting up datagroups in LookML.