The ability to create user-context aware calculated columns in Power BI has recently been released in preview. https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-calculated-columns
If I try to use ALM Toolkit to update a model that includes this functionality then I get the error message
"CUSTOMDATA, USERNAME, USERCULTURE and USERPRINCIPALNAME functions are not supported in calculated tables/columns. These functions may only be used in Measures or in the AllowedRowsExpression."
This happens whether the column in question is in the target or the source. It even happens if I am not trying to update the object with the calculated column but, rather, some other object in the model.
My question is if there is a fix for this in the pipeline?
The ability to create user-context aware calculated columns in Power BI has recently been released in preview. https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-calculated-columns
If I try to use ALM Toolkit to update a model that includes this functionality then I get the error message
"CUSTOMDATA, USERNAME, USERCULTURE and USERPRINCIPALNAME functions are not supported in calculated tables/columns. These functions may only be used in Measures or in the AllowedRowsExpression."
This happens whether the column in question is in the target or the source. It even happens if I am not trying to update the object with the calculated column but, rather, some other object in the model.
My question is if there is a fix for this in the pipeline?