Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreThe FabCon + SQLCon recap series starts April 14th at 8am Pacific. If you’re tracking where AI is going inside Fabric, this first session is a can't miss. Register now
Hi,
I'm on this exercise https://microsoftlearning.github.io/mslearn-fabric/Instructions/Labs/04-ingest-pipeline.html#create-... but I don't seem to be able to select the new_data folder as a location to store the sales csv. Would someone know why I'm getting this error message?
The new_data subfolder has already been created
Thanks Antoine,
Just to give you an update, I've tried recreating the destination but I still receive the same error. So I deleted the activity and started from scratch again but now I'm facing the error below. I think I will try deleting and recreating again.
Hi, unfortunately I am. This is what's happening now. I've recreated the connection. still didn't work so I went to connections and tried to log in again but it doesn't like my credentials. But its the same account i used when I created the connection. I don't have any other accounts.
Hi @DataUnicorn,
Thank you @AntoineWm, for your insights.
Delete the faulty Lakehouse connection from Settings Manage connections and gateways. Create a new Lakehouse connection using the Copy Data activity and sign in with your Microsoft account. Once you see the green check mark, set the destination path to Files/new_data/sales.csv and confirm you have Member or Admin permissions in the workspace. After authentication is restored, you’ll be able to browse folders normally and select the new_data folder in the pipeline without errors.
Thank you.
Hi,
I've just tried this and it's still giving me the same issue. I'm the workspace admin. SO when I create the connection, it accepts my credentials.
But when I try to browse the location, it comes up with the same error
Hi @DataUnicorn,
Since the issue persists even after recreating the Lakehouse connection and verifying your workspace permissions, it is likely a backend issue. Please submit a Microsoft Support ticket so the engineering team can review the activity ID and workspace logs.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thak you.
Hi @DataUnicorn,
I've encountered the same issue before, In my case, the problem came from a invalid connection in the pipeline.
Here’s what worked for me:
Go to the destination step in your pipeline.
Delete the existing connection that points to the Lakehouse.
Create a new connection and reconfigure the destination.
After recreating the connection, the pipeline ran normally again.
Antoine
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 15 | |
| 7 | |
| 6 | |
| 5 | |
| 4 |