Forum Discussion
DataSource.Error: ADBC: UnknownError while running a query with left join
- 1 year ago
Hello, CansuT ,
You can try double-checking the selection to ensure that there are no duplicate column names, so use aliases for every column. Also, if possible, wrap your request inside Value.NativeQuery (with EnableFolding=true) function that should help with ensuring it folds back to source. Alternatively, if you have non-common data types for Power BI, you can try to normalise them in the select itself.
Native Query syntax:
Value.NativeQuery(GoogleBigQuery.Database(...), SqlAsText, null, [EnableFolding = false])
Hello, CansuT ,
You can try double-checking the selection to ensure that there are no duplicate column names, so use aliases for every column. Also, if possible, wrap your request inside Value.NativeQuery (with EnableFolding=true) function that should help with ensuring it folds back to source. Alternatively, if you have non-common data types for Power BI, you can try to normalise them in the select itself.
Native Query syntax:
Value.NativeQuery(GoogleBigQuery.Database(...), SqlAsText, null, [EnableFolding = false])There weren't any duplicate/ambigious column names but using aliases everywhere solved this issue.
It used to be okay to not use aliases when there the column only existed in one of the tables. Has there been a change on Google's side that led to this issue now?