Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi,
I am on a trouble when trying to run a piece of code based on semantic-link-labs on a notebook when the notebooks is included on a pipeline.
The code is the one below
I know that the pip command can not be used when the notebook is scheduled (as part of the pipeline) and that an environment has to be created to include the libraries.
I create an environment as the follwoing one
but when I execute the notebook on a session using this environment folloing error is triggered
what are we doing wrong? There is some missing library on the environment?
I found a similar post wirh same error but no answer was provided....
Regards,
Alfons
Solved! Go to Solution.
Hi @alfBI , Thank you for reaching out to the Microsoft Community Forum.
Your code is correct. The error is likely due to the scheduled notebook pipeline not using an environment that includes semantic-link-labs. Add it to your Fabric environment explicitly and the issue may be resolved. Please check it once and share your results.
If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi @alfBI , Thank you for reaching out to the Microsoft Community Forum.
Your code is correct. The error is likely due to the scheduled notebook pipeline not using an environment that includes semantic-link-labs. Add it to your Fabric environment explicitly and the issue may be resolved. Please check it once and share your results.
If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Yes, the problem was that the environment was not propely updated (see the Last Update column of some libs was not updated).
Thx