Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
There was a problem refreshing the dataflow: 'Something went wrong, please try again later. If the error persists, please contact support.'. Error code: EntityUserFailure. (Request ID: 460e8fb5-e1f7-4477-a39e-2e720a3b56e3).
Apply_tbl_Activity_Incremental_Over_Periods: There was a problem refreshing the dataflow: 'Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: The value does not support versioning. Details: Reason = Expression.Error;ErrorCode = 10855;Detail = #table({"ID", "DateTime", "Performed By", "Action", "Comments", "UpdateDate", "DWH Last Updated At", "for_filtering_ir"}, {});Microsoft.Data.Mashup.Error.Context = User GatewayObjectId: 08a260a3-97fa-4307-bb55-6046f036f912'. Error code: 104100. (Request ID: 460e8fb5-e1f7-4477-a39e-2e720a3b56e3).
Dataflow gen2 fails with the above error.
I am ingesting dat from on prem sql server with incremental refresh to a lakehouse
Hi @smpa01
Mashup error code 10855 is defined as
Mashup Table: Appears to be an empty table with defined columns but no data.
Ensure your query returns at least one row by adding something like
if Table.IsEmpty(Source) then ... else ...
It would also be helpful if you paste the query into power BI so you can go through each transformation to identify the exact point the flow fails.
Thanks for this. This table has incremental refresh baked in which might result in a an empty table. i am not sure how that needs to be handled for lakehouse ingestion.
This part should be internally baked in to incemental refresh -
if Table.IsEmpty(Source) then ... else ...
@miguel can you please provide some insights on to why df gen2 keeps on faikling for some tables from on prem sql db. I keep on getting this, I am trying to ingest a base table without incremental refresh and it is still failing
I'm not sure sure that we can help with the information shared on this thread. Do you have a way for us to repro the behavior or could you go into details as to how we could create something similar in our own environments ? Or perhaps a more detailed definition of your mashup document ?
assuming that you're using the latest version of the gateway, please raise a support ticket so our engineering team can take a closer look at this scenario
To reproduce
#1. Ingest a data from on prem sql server to a lakehouse with fixed schema and replace using a df gen2. Do not factor in incremental refresh.
There is no issue in this step.
#2. Go back and factor in incremental refresh in the same df gen2 and run the dataflow. It errors out in this stage with 10855.
#3. If you factor in incremental refresh in #1 before doing a base ingestion, it gets error out with tge same error.
What I desire is to be able to ingest from on prem sql server db to lakehouse with incremental baked in without any error.
I keep on getting refresh error 104500, do you know what it is for?
There was a problem refreshing the dataflow: 'Something went wrong, please try again later. If the error persists, please contact support.'. Error code: 104500. (Request ID: f356ef9a-2194-46be-8aa2-72483c85d585).
dim_activity_WriteToDataDestination: There was a problem refreshing the dataflow: 'Something went wrong, please try again later. If the error persists, please contact support.'. Error code: 999999. (Request ID: f356ef9a-2194-46be-8aa2-72483c85d585).
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
50 | |
28 | |
14 | |
14 | |
4 |
User | Count |
---|---|
65 | |
59 | |
23 | |
8 | |
7 |