Forum Discussion
Resolver IGen2 Dataflows - Again appear to have serious issues.
I created a support ticket, 2402060040005927. However, after investigating, think I have identified the root cause. When creating a function, I'm adding a Blank Query and then pasting the M code into the Blank Query definition. That apparently is the root cause. And from that point on, I'm toast. When returning to the dataflow now, the Enable Staging option on that newly created function is disabled, but.....is apparently set to true. And bam, the error is there and cannot be resolved.
To create a function correctly, add a Blank Query and go through without changing. When in the dataflow screen, after creating the let Source = "" in Source query, uncheck the Enable Staging option. Then edit that query with the function definition.
It would be interesting to see if someone else sees the same behaviour in their Fabric tenant.
Hi MartinMason ,
Thanks for using Fabric Community.
Apologies for the issue you have been facing. I would like to check are you still facing this issue?
It's difficult to tell what could be the reason for this performance.
I'd highly recommend reaching out to our support team by raising a support ticket so an engineer can take a closer look at your situation:
Resolver II created a support ticket, 2402060040005927. However, after investigating, think I have identified the root cause. When creating a function, I'm adding a Blank Query and then pasting the M code into the Blank Query definition. That apparently is the root cause. And from that point on, I'm toast. When returning to the dataflow now, the Enable Staging option on that newly created function is disabled, but.....is apparently set to true. And bam, the error is there and cannot be resolved.
To create a function correctly, add a Blank Query and go through without changing. When in the dataflow screen, after creating the let Source = "" in Source query, uncheck the Enable Staging option. Then edit that query with the function definition.
It would be interesting to see if someone else sees the same behaviour in their Fabric tenant.
- Timal
Helper I
Hey,
Thanks man, you've saved me a lot of time.
Apprently this seems to be an issue (again?) still.
I was getting this issue while using a query as variable e.g.
let
Source = Date.Month(Date.AddMonths(Date.From(DateTime.LocalNow()), -1))
in
Source
Staging is enabled by Default when creating a blank query but i was in Fact able to just disable staging and fix the issue.However in the PowerQuery Editor it obviously worked fine and just as soon as i hit refresh it published successfully but failed loading.
TLDR; if you're using a custom (blank) query to output anything else than an actual Table you have to disable Staging
Hi MartinMason ,
I would like to check once again with you, whether your issue was resolved? Or still support team is looking into your issue?
Incase if any help is required from my end, let me know.
Thanks,
Gopi Krishna Chenna- MartinMason
It's been resolved. It's impossible to create the situation I was running into two days ago because now when you try to publish a dataflow and a function is created with Enable Staging checked (option was disabled for functions two days ago), you get an error that at least one of the queries in the dataflow does not contain a schema.
Hi MartinMason ,
Glad to know your query got resolved.
Please continue using Fabric Community for your further queries.
- Element115
Memorable Member
That makes two of us, frustration-wise. Testing right now my DF that contains the DimTable generating function...
- Element115
Nope... still works on my end... publish+refresh and no errors.
