Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi guys,
In our architecture we have main model, which is used by all reports (in Composite mode). Few weeks ago we encountered an error
We found that it is related to Calculation Groups, if Calulation Item contains arithmetic operation
example:
SELECTEDMEASURE() + 1
issue appears,if we remove any arithmetic operations
example:
SELECTEDMEASURE()
everithing works fine. Note in the visualization there are no measures which use Calculation Items.
In example above there is one simple measure: CNT Rows = COUNTROWS(SEATS). And column from the same table
Trace file info:
DataMashup.Trace Information: 24579 :
{
"Start": "2022-09-15T10:37:09.1702136Z",
"Action": "PBI.DS.ExecuteSemanticQueryInfo",
"message": "{\"ID\":\"0\",\"DSQG\":{\"NumSelects\":3,\"Reduction\":{\"DataVolume\":3,\"MaxInters\":1000,\"Primary\":{\"Init\":{\"Kind\":\"Top\"},\"Final\":{\"Kind\":\"Top\",\"Args\":[\"1000\"]}}}},\"DSQT\":{\"QueryPattern\":\"SuperDax\",\"Constraints\":[{\"Id\":\"DS0\",\"GroupEntities\":1,\"TotalM\":1,\"RelatedM\":1}]},\"PROC\":{\"ConnCategory\":\"Internal\",\"DsrVersion\":2},\"ERR\":\"Details: ErrorCode=QueryUserError, ProviderErrorCode=0xC1060000, ErrorSource=User, Message=Failed to move the data reader to the next row., HResult=0x80004005, Language=en-US, ProviderErrorMessage=[<ccon>OLE DB or ODBC error: An unexpected error occurred (file 'xldqsqlqueryfragment.cpp', line 105, function 'GenASQLTypeInternal'). \\n \\nTechnical Details: \\nRootActivityId: 018104bc-dd55-45be-b0eb-1eeeecf9e892 \\nDate (UTC): 9/15/2022 10:37:08 AM.</ccon>], ProviderGenericMessage=[OLE DB error: OLE DB or ODBC error.], ErrorSourceOrigin=MsolapWrapper, OnPremErrorCode=, InnerErrorDetails=[Type=MsolapWrapper.MsolapWrapperException, Message=Failure encountered while getting the next row in the result-set]\",\"MODEL\":{\"Caption\":\"<ccon>d4b2094c-f47d-49f3-bc1b-93db95390a63</ccon>\",\"Entities\":58,\"EntitiesNameLength\":702,\"Props\":824,\"PropsNameLength\":16047,\"Rel1To1\":18,\"Rel1ToM\":73,\"Kind\":\"Tabular\"},\"METRICS\":{\"Requested\":1,\"Actual\":1,\"Query\":1,\"Events\":5}}",
"sessionId": "88c7412d-cc4a-4d72-8497-40301a70100a",
"deviceId": "b104405e",
"userId": "61a965f4-3a18-4b15-acd9-96e30a31d01a",
"isInternal": "False",
"authenticatedUserId": "9abbc246-c159-4b49-85cf-1587501260d5",
"ProductVersion": "2.109.642.0 (22.09)",
"ActivityId": "ed2f67f2-81d3-409c-9991-41db6699a299",
"Process": "PBIDesktop",
"Pid": 21948,
"Tid": 12,
"Duration": "00:00:00.0003830"
}
Hi @sergii1988 ,
Please check the type of the column, maybe the error is caused by the incorrect type of the column.
Best regards,
Yadong Fang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
When I choose Table visualization, everything works fine
And if I shwitch to donut chart, the issue appears, not sure this is related to column type.
Before September everything worked fine, we didn't add any changes to our main model
Also in the trace file I see error message
ErrorSource=User, Message=Failed to move the data reader to the next row.
Check out the July 2025 Power BI update to learn about new features.
User | Count |
---|---|
72 | |
72 | |
38 | |
31 | |
26 |
User | Count |
---|---|
97 | |
86 | |
43 | |
40 | |
35 |