Forum Discussion
Caculate, Filter Agrument is CAPS sensitive
Why is the filter argumenets in the calculate function CAPS sensitive? see below screenshots as reference showing identifical expressions with the logical statement changed to lowercase.
Joerobert,
In my first reply, I am using SQL Server data source.
I test the connection to Oracle in April update of Power BI Desktop, in import mode, filter argument is not case sensitive.
However, in DirectQuery mode, filter argument is case sensitive, which inherits the "case sensitive" mode from Oracle, I execute a simple query in Oracle SQL Developer and find that the query will not return any values when I specify "COMPLETE" value.
Regards,
Lydia
4 Replies
Joerobert,
I am unable to reproduce your issue in April version of Power BI Desktop. I note that you are using Directquery mode, what is your data source and what is your Power BI Desktop version?
Regards,
LydiaThat is correct, i am pulling in data from an oracle database. Also I am using version: 2.56.5023.1021 64-bit (March 2018). There is a one month delay from when the PBI updates are pushed out across my organization so I will attempt to replicate this again later this month.
thanks
Joerobert,
In my first reply, I am using SQL Server data source.
I test the connection to Oracle in April update of Power BI Desktop, in import mode, filter argument is not case sensitive.
However, in DirectQuery mode, filter argument is case sensitive, which inherits the "case sensitive" mode from Oracle, I execute a simple query in Oracle SQL Developer and find that the query will not return any values when I specify "COMPLETE" value.
Regards,
Lydia
