microsoft / microsoft/Analysis-Services
ALM Toolkit compare does not work with user-context aware calculated columns
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 732
- Forks
- 433
- PR merge metrics
- No merged PRs in 30d
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ALM Toolkit comparison pipeline and reproduce the failure using a model containing a user-context aware calculated column, as described in the issue. Verify behavior when the column is in either source or target and when another object is updated; done means the comparison and update complete without the reported validation error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100