I think this is a much needed idea. Parameters go some way to solve this, but it is very lacking. The ability for users to be able to build the view they way by selecting the measure columns used in a table would be so powerful and enable streamlined designs.

TABLE IN WORKBOOK: Sales Region, Month, Account, USD North America, Jan-22, Revenue, 100K DATASET: Region, Country, State, Month, TransactionID, AccountType, GLAccount, Description, OrigCurrency, USDAmount On Expansion would show: Region, Country, State, Month, TransactionID, AccountType, GLAccount, Description,…

Hi, yes that is correct. After raising an SR regarding this, I was told that OAC only supports a single key. Hence the request to add support for multiple. Also note, the metadata retrieval for a single key does not seem to refresh, if the PK access changes in BigQuery.