microsoft / Microsoft-Fabric-workload-development-sample

Demonstrates how to implement a Microsoft Fabric workload in .net and typescript
Other
30 stars 16 forks source link

Issues with Workloads Hub and Workload Validation error message #143

Closed tdraganidis closed 1 week ago

tdraganidis commented 2 weeks ago

Trying to start using the Fabric WDK, but having a lot of issues with Fabric portal and Workloads.

Image

I don't have any custom workloads, I have just entered the Fabric portal.

Any suggestions on what I can do to start seeing the Workloads Hub and what this error is all about?

anitamayorov commented 1 week ago

Hi @tdraganidis, The workload hub is visible only when you have public workloads or activated to tenant workloads. Regarding the notification - when you turn on the developer mode experience, it searches for your local server to fetch your local workload. If you still haven't done the 'npm start' stage here https://learn.microsoft.com/en-us/fabric/workload-development-kit/quickstart-sample#set-up-the-sample-project then Fabric portal fails to locate the server and displays this notification.

tdraganidis commented 1 week ago

Hi @tdraganidis, The workload hub is visible only when you have public workloads or activated to tenant workloads. Regarding the notification - when you turn on the developer mode experience, it searches for your local server to fetch your local workload. If you still haven't done the 'npm start' stage here https://learn.microsoft.com/en-us/fabric/workload-development-kit/quickstart-sample#set-up-the-sample-project then Fabric portal fails to locate the server and displays this notification.

Hi @anitamayorov, thanks for your prompt reply!

Am I missing any other settings that should be applied in another place?

anitamayorov commented 1 week ago

Hi @tdraganidis ,

This workload hub is currently not visible unless you have public workloads or activated to tenant workloads. So per your development scenario, you will not be able to see the workload hub at the moment. This behaviour is expected to change, no ETA.