Denodo causing ODBC error

[Power_It_Up]

Afternoon.

I have a Denodo script which has run perfectly well until I added this statement:

CAST(

CASE
WHEN g.caseid = '1234' AND r.priority = 'Y'
THEN '1234Y'
WHEN g.caseid = '1234'
THEN '1234N'
ELSE g.caseid
END
AS VARCHAR) AS "CASEID"

This is the error:

I've tried wrapping the CASE statement with TEXT, VARCHAR and tried other solutions, but to no avail.  The g.caseid field in Denodo is type text.

When leaving the statement as ' g.caseid AS "CASEID" ' it runs fine.  If I filter out id 1234 prior to applying the change, the script runs fine.  It deosn't seem to like me adding a Y or N after 1234 even though the field is text.

Help! lol

Regards,

P.

[cengizhanarslan]

Power BI caches column metadata. After changing the Denodo view/query, in Power Query you may need to:

• Clear cache / refresh preview

• Or remove/recreate the step that defines the source schema

[Power_It_Up · Accepted solution]

@cengizhanarslan Thank you for replying. I tried the refresh preview prior to executing the query but it still shows the same error.

Edit: I opened a fresh workbook and placed my query in that and it's working fine! I can't re-create the whole workbook, but this is interesting.

Edit2: I added a duplicate Denodo query in the existing problematic workbook and this one is executing fine.  So something is causing the original query to fail.

[v-ssriganesh]

Hi @Power_It_Up,

Thank you for the update. We appreciate your efforts and are glad to hear that the issue has been resolved.

Your findings are valuable and will certainly help other community members who may encounter similar behavior related to cached metadata in Power BI.