Home > Known Issues
Download this articleKnown Issues
| Known Issues | Identified in Version |
|---|---|
| Users who are assigned the Site sponsor permission through security group membership will not see any sites displayed in SharePoint reports. This occurs because the current data processing and reporting logic does not harvest or resolve security group membership.Workaround: Assign the Site sponsor permission directly to individual users rather than to security groups to ensure sites are displayed correctly in reports. | February 2026 |
| Sponsors without existing SharePoint site permissions cannot see or interact with the SharePoint web part because the Site sponsor role in tyGraph does not elevate SharePoint access. | February 2026 |
| When using the Import function to create custom properties, attributes may be automatically numbered if the property name matches one from Entra ID. This is to avoid duplicate property names, which are not permitted in Power BI. | April 2025 |
| Users with full control permissions for SharePoint classic sites may encounter an issue where these sites do not appear in the Reports > Sites that I own section. | December 2024 |
| ● Due to the absence of the tyGraph Power BI template apps in the GCC environment, users are unable to view Power BI embedded reports through the installation of related reporting tools in Microsoft Power BI. | December 2024 |
| ● After the tyGraph Pages Web Parts app package has finished uploading to SharePoint, the app may fail to be added to Teams, even if the Add to Teams option was selected in the Enable app panel during the app’s activation .● Workaround: Select the uploaded tyGraph Pages Web Parts app on the Manage apps page and click Add to Teams. | June 2024 |
On this page