Forum Discussion
Issue with Loading Retail Data Model from Wide World Importers into Data Warehouse on Fabric
Dear Community Support,
Thank you for your follow-up. I have opened a support ticket.
The ticket number is 2407030030009040.
Please let me know if there’s any additional information you need.
Best,
Ahmad
Hi, have you received a response yet? Thanks.
- ahmadammari2 years agoAdvocate I
Yes. I have received the following response from the Microsoft Support Team:
```
Dear Ahmad,
Thank you for reaching out to us regarding the issue with loading the Retail Data Model from Wide World Importers. I understand that you have been waiting for updates on this matter, and I apologize for any inconvenience caused.
After discussing with the product team and the Wide World Importers dataset owner, we have confirmed that the issue is related to a company-level security policy. Our team is actively working on the recovery process, but unfortunately, we do not have an estimated time of completion at this moment. As a result, we have decided to hide the Wide World Importers dataset on the data pipeline UI.
I would like to suggest that you consider using other sample datasets available to you. We have a variety of datasets that you can choose from, which will still allow you to explore and work with our platform effectively.
If you have any further questions or need additional assistance, please don't hesitate to reach out to me. I will be more than happy to help you.
Thank you for your understanding and cooperation.```
- TarikQAZZABARI11 months agoRegular Visitor
Hi everyone,
If you're running into issues using .parquet file links directly in Fabric, here's a tip that helped me resolve it.
Fabric doesn't support referencing individual .parquet files via HTTPS in SQL commands. Instead, you should point to the directory containing the files—without including the .parquet extension.
For example, use this base path:
Codehttps://fabrictutorialdata.blob.core.windows.net/sampledata/WideWorldImportersDW/parquet/full/
And reference the folder name (not the file) in your COPY INTO statement like this:
sqlCREATE PROCEDURE dbo.LoadStageTablesAS BEGIN COPY INTO [stage].[DimDate] FROM 'https://fabrictutorialdata.blob.core.windows.net/sampledata/WideWorldImportersDW/parquet/full/dimension_date' WITH (FILE_TYPE = 'PARQUET'); COPY INTO [stage].[FactSale] FROM 'https://fabrictutorialdata.blob.core.windows.net/sampledata/WideWorldImportersDW/parquet/full/fact_sale' WITH (FILE_TYPE = 'PARQUET');END; EXEC dbo.LoadStageTables;
This approach works because Fabric expects a folder path containing one or more .parquet files, not a direct file reference. Hope this helps someone else avoid the same confusion!