Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
scoutmedic
Helper I
Helper I

Power BI Service fails to update despite no errors reported in Desktop

I recently created a report in PowerBI Desktop and all works as expected. I published the report to PBI Service and have multiple failed refreshes. The error states:

"Expression.Error: There weren't enough elements in the enumeration to complete the operation.. #table({"Content", "Name", "Extension", "Date accessed", "Date modified", "Date created", "Attributes", "Folder Path"}, {}). ;There weren't enough elements in the enumeration to complete the operation.. The exception was raised by the IDbCommand interface. Table: Main Hierarchy."

 

I cleared the cache in Desktop and refreshed each table individually without issues.

 

None of my tables are displaying any errors. I've checked all data source credentials and no errors are reported. RLS is disabled. (I don't think these are the issues, but worth mentioning.)

 

Thoughts on how to proceed? 

1 ACCEPTED SOLUTION

I went through and deleted a few unused helper queries and the issue resolved.

View solution in original post

5 REPLIES 5
scoutmedic
Helper I
Helper I

I confirmed my date slicer is set to "All" and my refresh timezone in Service matches my timezone. 

 

I deleted the semantic model from Service, cleared my cache, restarted, refreshed locally and no errors occurred. I published it again, verified refresh settings, and still had the same issue. I did confirm my permissions were all set to none in Desktop before publishing. Thought maybe it wouldn't refresh if permissions didn't match, but that wasn't it either.

You seem to be trying to ingest files from a folder. Is it on a sharepoint?  Is it maybe a folder on your C: drive?

 

Please show a sanitized version of the Power Query code.

I recreated the query but reordered the operations and still received the same error for the new query. This table is being used in other reports without issues.

 

I've isolated it to this table:

 

let

    Source = SharePoint.Files("httpsxxxxxxxxxxxxx, [ApiVersion = 15]),

    #"Filtered Rows" = Table.SelectRows(Source, each ([Name] = "FileName.xlsx")),

    #"Filtered Hidden Files1" = Table.SelectRows(#"Filtered Rows", each [Attributes]?[Hidden]? <> true),

    #"Invoke Custom Function1" = Table.AddColumn(#"Filtered Hidden Files1", "Transform File (13)", each #"Transform File (13)"([Content])),

    #"Renamed Columns1" = Table.RenameColumns(#"Invoke Custom Function1", {"Name", "Source.Name"}),

    #"Removed Other Columns1" = Table.SelectColumns(#"Renamed Columns1", {"Source.Name", "Transform File (13)"}),

    #"Expanded Table Column1" = Table.ExpandTableColumn(#"Removed Other Columns1", "Transform File (13)", Table.ColumnNames(#"Transform File (13)"(#"Sample File (13)"))),

    #"Changed Type" = Table.TransformColumnTypes(#"Expanded Table Column1",{{"Source.Name", type text}, {"A", type text}, {"B", type text}, {"C", type text}, {"D", type text}, {"E", type text}, {"F", type text}, {"G", type text}, {"H", type text}, {"I", type text}, {"J", type text}, {"K", type any}, {"L", type text}, {"M", type text}, {"N", type text}, {"O", Int64.Type}, {"P", type text}, {"Column17", type any}}),

    #"Filtered Rows2" = Table.SelectRows(#"Changed Type", each ([A] = "xxx" or [A] = "xxx") and ([B] <> "x" and [B] <> "y" and [B] <> "z")),

    #"Removed Other Columns" = Table.SelectColumns(#"Filtered Rows2",{"A", "B", "C", "D"}),

    #"Renamed Columns" = Table.RenameColumns(#"Removed Other Columns",{{"A", "W"}, {"B", "X"}, {"C", "Y"}, {"D", "Z"}}),

    #"Removed Duplicates" = Table.Distinct(#"Renamed Columns", {"Z"})

in

    #"Removed Duplicates"

 

I have not manipulated the queries yet.

I went through and deleted a few unused helper queries and the issue resolved.

lbendlin
Super User
Super User

That error usually indicates empty tables.  Do you have date filters in your Power Query?  Is your local timezone different from UTC?

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.