Unknown credential for dsn

[Planky]

I am using the following odbc query to get data from AWS Athena.

let
    Source = Odbc.Query("dsn=master", "Select * from data WHERE year >= " & DateTime.ToText(RangeStart, "yyyy") & "
AND month >= " & DateTime.ToText(RangeStart, "MM") & "
AND year < " & DateTime.ToText(RangeEnd, "yyyy") & "
")
in
    Source

The rows download and I can see the status change to detecting relationships before it fails with the following:

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.108.603.0","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.QueryFolding.FoldedArtifactsGenerator","Error":"System.InvalidOperationException","MethodDef":"GetUserInfo","ErrorOffset":"43"}

In another report, I am able to use odbc.datasource with the same dsn without issue - I receive no credentials error. The main difference here being that its not leveraging query folding:

  Source = Odbc.DataSource("dsn=master", [HierarchicalNavigation=true]),
    AwsDataCatalog_Database = Source{[Name="AwsDataCatalog",Kind="Database"]}[Data],
    billing_Schema = AwsDataCatalog_Database{[Name="billing",Kind="Schema"]}[Data],

I can provide the additional power bi error details/trace logs/etc on request

[v-yetao1-msft]

Hi @Planky 

So I have a doubt , if you can connect to AWS Athena with no issue in other report , why did you use the power query below ?

Best Regards,
Community Support Team _ Ailsa Tao

[Planky]

Because using the other method does not work with query folding and results in full table scans, loading the entire table every refresh. It prevents incremental refresh from working.

Using the ODBC query above correctly scans the appropriate partition(s) for the date ranges specified via the rangeStart / rangeEnd parameters and downloads a much smaller subset of data as a result; Incremental refresh works correctly.

Regardless, using odbc.query against Athena shouldnt result in the error reported

Cheers!

[charurock]

Hi,

I am following as I have exact same pain..Because using the other method does not work with query folding and results in full table scans, loading the entire table every refresh. It prevents incremental refresh from working.

any resolution will be much appreciated.

@Planky , did u receive any solution?

[Adam3]

Hi, 

I had the same issue and I found a way how to set up the query with incremental refresh.

Instead of adding parameters directly into a query, create a function and then call it in the query.

Function:

Query:

[Planky]

@charurockNo, I didn't. I long since abandoned this approach as no fix or acknowledgement from MS was ever provided.

@Adam3Im not certain that would avoid the issue of full table scans but I've don't have anyway to test so I'd have to take your word for it.