The filters restrict the data to the target Yammer groups. The Power BI documentation describes the process for creating roles. Logic would suggest that applying a Table Filters to: In order to limit TyGraph data to specific Groups it is necessary to apply Table Filters to: Each role in our model has access to a specific set of data. The filters are applied through Manage roles: However this will result in visualisation errors owing to the way Relationships are defined in the model. The Table filter DAX expression filters the data based on the GroupID. To filter for more than one GroupID (This Group OR That Group): = 13338219 || = 9020365 Effect of Relationships Thankfully filtering only needs simple DAX expressionsįor example, to filter for a single GroupID: = 13338219 This removes the risk where a Group is renamed. It is important to note that owing to the way TyGraph have defined Relationships in the model several items may still display names of Groups that are outside of the Role definition.Slicers using fields from the Groups table.

However the messages and activities that are outside of the Role definition will not be displayed. This is overcome and the presentation of the Report tidied up using a Report level filter that includes the Groups used in the Role definitions: This is acceptable to us as message content is not exposed. Note that a user could delete this filter in the published report thinking that it would expose more data. The worst that happens is the Group names are revealed which is no different to Yammer whereby names of Private groups are visible unless the group is removed from the directory. To illustrate, with Report level filter applied: However RLS will prevent out of Role data from being shown. The Power BI documentation describes the process through which you can validate the correct application of the Roles. You cannot assign users to a given role in Power BI Desktop. Assignment is achieved using the web version of Power BI.

Tygraph for sharepoint