The column 'FX_RATES[CONVERSION_RATE]' either doesn't exist or doesn't have a relationship to any ta

[vmuralimohan]

I have two tables

1) GL_QA :- this is a direct query from SQL server

2) FX_RATES :- this is loaded from share point Excel file

Created a calculated column on both for joining the two tables

FX_RATES (one) to GL_QA(Many) relation is created

i am trying to create a new CALCULATED column on GL_QA table using RELATED function to get FX_RATES .CONVERSION_RATE   

and getting an error

The column 'FX_RATES[CONVERSION_RATE]' either doesn't exist or doesn't have a relationship to any table available in the current context.

Any help

[Anonymous]

Hi @vmuralimohan ,

Please check the document below and see the limitationa in calculated column on Direct Query mode.

https://docs.microsoft.com/en-us/power-bi/desktop-directquery-about#implications-of-using-directquer....

Best Regards,

Jay

Community Support Team _ Jay Wang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[JarroVGIT · Accepted solution]

Hi @vmuralimohan ,

The MSFT documenation says the following:

Limitations in calculated columns: Calculated columns are limited to being intra-row, as in, they can only refer to values of other columns of the same table, without the use of any aggregate functions. Additionally, the DAX scalar functions, such as LEFT(), that are allowed, are limited to those functions that can be pushed to the underlying source. The functions vary depending upon the exact capabilities of the source. Functions that aren't supported aren't listed in autocomplete when authoring the DAX for a calculated column, and would result in an error if used.

So, it doesn't seem you are able to incorporate RELATED() function in calculated column on a directquery query.

Kind regards

Djerro123

-------------------------------

If this answered your question, please mark it as the Solution. This also helps others to find what they are looking for.

Keep those thumbs up coming! 🙂