Power BI Error Reference_

Paste the error. Get the cause and the fix.

38 DAX, Power Query and Power BI errors, each on its own page — what it means, why it happens, and how to fix it. No sign-in, no video, no fluff.

DAXA circular dependency was detected.Two or more calculated columns, measures or tables depend on each other, directly or through filter context. DAXA function 'X' has been used in a True/False expression that is used as a table filter expression. This is not allowed.A boolean filter argument to CALCULATE or CALCULATETABLE contains something not allowed there — usually a measure or a multi-column aggregation. DAXA single value for column 'X' in table 'Y' cannot be determined.A measure or calculated column referenced a bare column that has many rows in the current context, but DAX needs exactly one value. DAXCannot convert value 'X' of type Text to type Number.DAX tried arithmetic or an implicit conversion on a text value that isn't a clean number. DAXColumn 'X' in table 'Y' cannot be found or may not be used in this expression.The column or table name is wrong, was renamed or deleted, or isn't valid in this context. DAXDAX comparison operations do not support comparing values of type Text with values of type Integer. Consider using the VALUE or FORMAT function.You compared a text value to a number. DAXEARLIER/EARLIEST refers to an earlier row context which doesn't exist.EARLIER was used without a surrounding (nested) row context to step back into. DAXThe column 'X' either doesn't exist or doesn't have a relationship to any table available in the current context.RELATED needs an active many-to-one relationship to the target table, and there isn't one. DAXThe expression refers to multiple columns. Multiple columns cannot be converted to a scalar value.A place that expects a single scalar value received an expression spanning more than one column. DAXThe result of a conversion or arithmetic operation is either too large or too small.An overflow or underflow, or an out-of-range value converted to a date/number. DAXThe syntax for 'X' is incorrect.A DAX parse error near the named token. DAXThere's not enough memory to complete this operation.A query or refresh needed more RAM than was available — often a huge cross join, a fan-out relationship, or high-cardinality keys. DAXToo many arguments were passed to the X function. The maximum argument count for the function is N.The function received more arguments than its signature allows. Power QueryAccess to the resource is forbidden. / The credentials provided for the data source are invalid.Power Query has no valid credentials or permission for the source. Power QueryDataFormat.Error: We couldn't convert to Date.A value can't be parsed as a date under the current locale. Power QueryDataFormat.Error: We couldn't convert to Number.A Changed Type step hit a value that isn't a valid number under the current locale. Power QueryExpression.Error: A cyclic reference was encountered during evaluation.A query references itself directly or indirectly. Power QueryExpression.Error: The column 'X' of the table wasn't found.A step references a column that doesn't exist at that point — usually renamed, removed, or a source schema change upstream. Power QueryExpression.Error: The key didn't match any rows in the table.A row or record lookup (for example Source{[Name="X"]}) found no matching row. Power QueryExpression.Error: We cannot apply field access to the type Text.You used record/field access (like [Field]) on a value that is text, not a record or table. Power QueryFormula.Firewall: Query 'X' (step 'Y') references other queries or steps, so it may not directly access a data source. Please rebuild this data combination.The privacy firewall blocked one step that both touches a data source and uses values from another query. Power QueryOLE DB or ODBC error: [provider] ...The database driver returned an error — a SQL problem, a driver/connection issue, or a timeout. Power QueryToken Comma expected. / Token Literal expected. / Token RightParen expected.An M syntax error — the parser expected a token that isn't there. PBIPCannot read 'definition.pbism'. Required artifact is missing.The semantic model is missing its definition.pbism file. PBIPChart visual projections structure — Category/Y/Series serialized as a dict under projections.The chart's projections use a dict where the schema expects arrays of field references per bucket. PBIPIncorrect field type in visual queries (Measure vs Column).A visual fails to load because fields are typed as Measure when they should be Column, or vice versa. PBIPInvalid background properties (imageFit, imageTransparency, imagePosition).A visual or page background uses image properties that aren't valid in the schema. PBIPInvalid indentation was detected!A TMDL file mixes spaces and tabs, or uses spaces to indent; TMDL requires consistent tab indentation. PBIPInvalid property in the .pbip artifacts array (semanticModel vs dataset).The .pbip file's artifacts array uses the wrong key for the model reference. PBIPInvalid visual query structure — projections and queryState at the wrong level.projections/queryState are nested at the wrong level, so the visual's query is invalid. PBIPProperty 'description' is unknown and is not expected in the situation it appears.A /// doc comment before a relationship created a description property, which relationships don't support. PBIPProperty 'drillFilterOtherVisuals' has not been defined and the schema does not allow additional properties.A visual.json contains drillFilterOtherVisuals, which isn't a valid property in the visual container schema. PBIPvisualContainerObjects is at the root level of visual.json (invalid position).visualContainerObjects must sit inside the visual object; at the root it's invalid and formatting silently breaks. ModelCan't determine relationships between the fields.A visual mixes fields with no relationship path between their tables, or an ambiguous one. ModelThe data type of column 'X' in the query doesn't match the data type in the model.A refresh produced a value that doesn't fit the column's declared type in the model. ModelYou can't create a relationship between these two columns because one of the columns must have unique values.A one-to-many relationship needs a unique key on the one-side, and the column you picked has duplicates. ServiceCouldn't load the data for this visual.The visual's query failed — commonly a timeout, a measure that errors under some filters, or a gateway/source issue. ServiceThis visual has exceeded the available resources.The visual's query is too heavy for the query resource limits.