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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
danielmccluskey
Regular Visitor

Something went wrong, Dataflow publish failed

Hi, Im getting a strange and vague error when I publish my data flow gen 2.

All I get is "Something went wrong" and can't seem to find out anything else about where it is going wrong.

 

I can publish without error but then I get:

 

(Clicking See details just shows me the IDs of the flow and what time the error occurred.)

Screenshot 2023-09-28 225627.pngScreenshot 2023-09-28 230203.png

 

 

let
    FetchPage = (url) =>
        let
            Source = Json.Document(Web.Contents(url)),
            Data = Source[data],
            NextPage = Source[meta][pagination][next],
            More = Source[meta][pagination][more],
            Result = if More then Data & @FetchPage(NextPage) else Data
        in
            Result,
    StartURL = "https://api.wonde.com/v1.0/schools?page=1",
    AllData = FetchPage(StartURL),

...and so on with some more data changes

 

 

1 ACCEPTED SOLUTION
danielmccluskey
Regular Visitor

I managed to solve this, I was changing the base URL of the Web.Contents which meant the flow didn't know what connector to use everytime it changed.

 

Fixed by using one Base URL and then using RelativePath and Query properly.

 

So I changed this

 

let
    FetchPage = (url) =>
        let
            Source = Json.Document(Web.Contents(url)),
            Data = Source[data],
            NextPage = Source[meta][pagination][next],
            More = Source[meta][pagination][more],
            Result = if More then Data & @FetchPage(NextPage) else Data
        in
            Result,
    StartURL = "https://api.wonde.com/v1.0/schools?page=1",
    AllData = FetchPage(StartURL),

...and so on with some more data changes

 

into this:

 

FetchPage = (url) =>
        let
            baseURL = "https://api.wonde.com/v1.0/",
            relativePath = "schools",
            queryList = Uri.Parts(url)[Query],
            response = Web.Contents(baseURL,
            [
                RelativePath = relativePath,
                Query = queryList
            ]),
            Source = Json.Document(response),
            Data = Source[data],
            NextPage = Source[meta][pagination][next],
            More = Source[meta][pagination][more],
            Result = if More then Data & @FetchPage(NextPage) else Data
        in
            Result,
    StartURL = "https://api.wonde.com/v1.0/schools?page=1",
    AllData = FetchPage(StartURL),

which means it always uses the same connector and is using the relative path correctly.

View solution in original post

8 REPLIES 8
MawashiKid2
Helper I
Helper I

I encountered similar issue recently with Dataflow Gen2 in Microsoft Fabric. I mean nothing really fancy here, only selecting a .csv file uploaded in Lakehouse folder which I had previously created, then define a destination through Add Data Destination to very same Lakehouse with new table name though in different folder. "Dataflow Failed to Publish!"  [sigh...]

Okay never mind... solved it! It seems Dataflow Gen2 didn't seem to accept any blank space after a comma... in csv. So I simply removed all blank spaces in original csv file, deleted the wrong formatted csv file version in Lakehouse, then re-uploaded new corrected csv version in same Lakehouse and it worked this time...just as stupid as that... [sigh...]

Interesting. 

 

How did you find out that it was the reason?

 

Was there some error values in some of the data columns?

To resume...
It turns out a Column name from a .csv sample file I had downloaded to use for simple SCD2 test- and had previously uploaded in a Lakehouse under Files folder - was not well formatted.
So I then created DataFlow Gen2 (WhateverDF...). Once the csv file as loaded in the DataFlow,
I then selected Use first row as header, defined a new Table name in same Lakehouse as destination using Add data destination, then simply clicked on Publish.
A popup notification displayed Dataflow WhateverDF failed to pulished! error.PopupError.png
I then located the WhateverDF Dataflow instance in main Workspace Name column and noticed a small red border triangle next to it.

ErrorDF.png

I simply clicked on it to get more details about the error.

ErrorDFDetails.png
So that was it. The Name column name was formatted as ', Name' when it should have been formatted as ',Name' that is with NO SPACE between the comma and first letter of column name. So I simply fixed the error and was then able to Publish and run DataFlow Gen2 as expected. N.B. The DataFlow Gen2 doesn't imply much transformation here - beside selecting first row as header - and is used mainly in combination with a Notebook in a data pipeline.  All SCD2 logic is defined in Notebook. That's when the rubber hits the road!😉 

Thank you for sharing!

Nice to learn that an explanatory error message for failed publishes can be found in the workspace interface (triangle icon) 😀

 

Since the error popup you received immediately when the publish failed, didn't seem to provide much guidance.

danielmccluskey
Regular Visitor

I managed to solve this, I was changing the base URL of the Web.Contents which meant the flow didn't know what connector to use everytime it changed.

 

Fixed by using one Base URL and then using RelativePath and Query properly.

 

So I changed this

 

let
    FetchPage = (url) =>
        let
            Source = Json.Document(Web.Contents(url)),
            Data = Source[data],
            NextPage = Source[meta][pagination][next],
            More = Source[meta][pagination][more],
            Result = if More then Data & @FetchPage(NextPage) else Data
        in
            Result,
    StartURL = "https://api.wonde.com/v1.0/schools?page=1",
    AllData = FetchPage(StartURL),

...and so on with some more data changes

 

into this:

 

FetchPage = (url) =>
        let
            baseURL = "https://api.wonde.com/v1.0/",
            relativePath = "schools",
            queryList = Uri.Parts(url)[Query],
            response = Web.Contents(baseURL,
            [
                RelativePath = relativePath,
                Query = queryList
            ]),
            Source = Json.Document(response),
            Data = Source[data],
            NextPage = Source[meta][pagination][next],
            More = Source[meta][pagination][more],
            Result = if More then Data & @FetchPage(NextPage) else Data
        in
            Result,
    StartURL = "https://api.wonde.com/v1.0/schools?page=1",
    AllData = FetchPage(StartURL),

which means it always uses the same connector and is using the relative path correctly.

Anonymous
Not applicable

Hi @danielmccluskey ,
Glad that your issue got resolved. Please continue using Fabric Community for help regarding your queries.

miguel
Community Admin
Community Admin

Hey!

I'd recommend that you raise a support ticket so an engineer can take a closer look at it.

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.

ArunFabCon

Microsoft Fabric Community Conference 2025

Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.

Top Solution Authors