microsoft / microsoft/Microsoft-Fabric-workload-development-sample
Job Details pane link to Lakehouse
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 58
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Workload Manifest Schema Version (if relevant)
No response
Your Question
I would like to put a link to a Lakehouse in the Job Details pane for my custom workload.
It should be possible because it works for a Lakehouse. Please see the attached screenshot.
I cannot find any documentation.
Context / Background
It does not work for my custom workload. THat particular label is not even present in the Job Detains pane.
This is the relevant object in the ItemJobActionResult / ItemJobDetailData / ItemJobDetailActionMetadataAttrs chain that I added
{
label: 'Output Destination URL',
type: 'link',
value: 'Output_LH',
url: outputDestination ,
},
where
outputDestination = "https://app.fabric.microsoft.com/groups/8c41c...8bf2fe64b1d4882b/lakehouses/225009a...0abe1b628290"
and it is a valid URL.
A screenshot of what I am getting is attached.
So far the only link that works is a link to open the custom workload item in its editor.
Additional References
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the ItemJobActionResult, ItemJobDetailData, and ItemJobDetailActionMetadataAttrs chain used by the custom workload, then compare it with the Lakehouse implementation shown in the issue. Verify how the Job Details pane handles the type: 'link' metadata and the Lakehouse URL; done means the output destination label appears and opens the supplied Lakehouse link.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 46/100