Forum Discussion
FUAM - FUAM_Core_SM - Refresh warnings
Hi,
We recently installed FUAM .
It all went smoothly, but when running the first refresh of FUAM_Core_SM semantic model (Step 7.1) we did get the following warning:
Cannot find table '<oii>workspace_monitoring_reports</oii>'.
Posting here because we were unsure whether this was expected (i.e can be safely ignored) or whether it was a problem we needed to resolve. Hoping someone here may have some info regarding this.
Possibly this is related to Fabric Workspace Monitoring Report Templates - Deployment Scenario D) Integration with FUAM ?
i.e. the table from the warning only exists if workspace monitoring reports are being integrated with FUAM, so the warning can be safely ignored if this integration is not in play ?
cheers
Hi amthog ,
Thank you for reaching out to the Microsoft Community Forum. This warning is expected in many setups and can usually be safely ignored unless you explicitly enabled Workspace Monitoring integration. FUAM’s Core semantic model (FUAM_Core_SM) is built to optionally include additional datasets/tables beyond the default pipeline outputs. One of those optional integrations is Workspace Monitoring. The table "workspace_monitoring_reports" is not a standard FUAM table it is only present when you deploy and integrate the Workspace Monitoring Dashboards solution and wire it into FUAM.
Note: You can remove warning by editing FUAM_Core_SM model, Removing or disabling references to "workspace_monitoring_reports".
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
4 Replies
- v-dineshya
Community Support
Hi amthog ,
Thank you for reaching out to the Microsoft Community Forum. This warning is expected in many setups and can usually be safely ignored unless you explicitly enabled Workspace Monitoring integration. FUAM’s Core semantic model (FUAM_Core_SM) is built to optionally include additional datasets/tables beyond the default pipeline outputs. One of those optional integrations is Workspace Monitoring. The table "workspace_monitoring_reports" is not a standard FUAM table it is only present when you deploy and integrate the Workspace Monitoring Dashboards solution and wire it into FUAM.
Note: You can remove warning by editing FUAM_Core_SM model, Removing or disabling references to "workspace_monitoring_reports".
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
- amthog
Helper I
Hi Dinesh,
Thanks for your quick response, and for confirming that the warnings can be safely ignored.
> Please do let us know if you have any further queries.
I do actually have two more questions.
The first is that I noticed several mistakes in the documentation when installing.
What is the most appropriate way to provide feedback on these ? Raise an issue in GH ?
Second, the Core Report has a page called 'Optimization Module' but it is unclear whether this is meant to be working or not and whether we need to do anything specific to enable it.
The Step 1, Step 2 and Step 3 visuals on the page all show no data.
The Introduction on the page says "The count of scoped semantic models for Optimization Module can be changed in the Load_FUAM_E2E pipeline' but there is no sign of a relevant parameter, nor any activities whose name mentions Optimization.
There is an Optimization Module folder created in the workspace post-deployment but it is empty.
The deployment_config.yaml does include the following entry for that folder:
- name: "Optimization Module"
items:
- 00_Run_Optimization_Module_for_SM_Unit.Notebook
However there is no 00_Run_Optimization_Module_for_SM_Unit.Notebook file in the repo, which presumably explains why the resulting folder is empty.
Can you confirm whether the Optimization Module page is meant to be working in this release (2026.2.1) and if so what we would need to do to enable it ?- v-dineshya
Community Support
Hi amthog ,
Please explore the Github, to raise an issue in Github. And It appears this issue might require deeper investigation from the Microsoft Fabric support team. I recommend opening a Microsoft support ticket so they can trace the issue. To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Regards,
Dinesh