- SAP Managed Tags:
Datapoint comment on table cell within story based on acquired model in SAP analytics cloud
In SAP Analytics Cloud, you can add comments on the table cell within story. In order to add comment, right click on the selected cell and then select add comment. These comments are associated with the models, which means, if the same model used in different story and has same table cell available then the comment will appear in those stories as well. You can view comment in the comment popup or in table column
Fundamentally, table cell represent a coordinate which get formed based on the dimensions/measures selected in the row, column and filters. Same cell can represent different aggregated value and this can happen for example when filter is applied or there is different data access control on the dimension member for different users.
Datapoint comment behaviour with Filter
In this example, I have a data for California state which consist of 4 cities which are Los Angeles, San Francisco, San Jose and Oakland, I am adding comment on quantity sold for California (which is aggregated value for the four cities)
This comment will be visible to user as long as they are seeing same table cell value (coordinates formed by all combinations). if I filter the dimension member of California to have 3 cities say Los Angeles, San Francisco and San Jose (fig 2) then the previously added comments will not be available as the table cell aggregation would change
I can apply filter on another dimension say product (Fig 3) then also the aggregation would change for the cell and the comment made earlier will not be visible
In all three fig 1, fig 2 and fig 3, we see different aggregation and the cell represent like below which makes them unique datapoints
Fig 1: Quantity sold in California for all product (where California consist of all four states)
Fig 2: Quantity sold in California for all product (where California consist of three states)
Fig 3: Quantity sold in California for product alcohol and carbonated drink (where California consist of all four states)
Datapoint comment behaviour with Data access control
On the similar line to filter, In data access control example (not the story/page filter), if we have two users John and Gary and for the state Nevada john has access to all four cities “ Carson city, Las Vegas, Reno and Henderson” however Gary has access to only two cities “ Las Vegas and Reno”. In this example comment added by
- John on Nevada will not be visible to Gary as the aggregation is different for both users when they see quantity sold for Nevada respectively in the table cell
- Gary will not be visible by default to John however if John does further filter at story level to view only Las Vegas & Reno city within the Nevada then the comment added by Gary will be visible to John as aggregation become same for john as it was for Gary
Data access control applied on a dimension member which is not part of the table
In the below example, Product is not part of the visible dimension in the table. Here Admin has access to all product members, however, Gary has access to limited product members; hence comments added by Admin is not visible to Gary and the comment added by Gary is not visible to Admin. However if admin explicitly filter the product member same as that Gary then the comment added by Gary will be visible to admin.
Datapoint comment behaviour with Data access control applied to leaf node of the dimension member and the access to new member is added and removed
Case 1:Providing access to new dimension member for non admin user (Gary)
In the below example, Product is not part of the visible dimension in the table. Here Admin has access to all Product members. Gary, who is Non admin, has access only to Coca-Cola, Pepsi and Sprite members of Product and comment is added on California.
Later, Gary has been provided access to few additional member Fanta, Diet Coke and Root Beer. even after this new access, Gary will continue to be able to see the comments added by him as the context of the comments are regenerated with new members which Gary got access to after this changes.
In Gary is the name and Temp is the ID
Initially, Gary (Non Admin user) access only to Coca-Cola, Pepsi and Sprite members and added comment
Later, Gary (Non Admin user) has been given access to few more member Fanta, Diet Coke and Root Beer, so now Gary has access to Fanta, Diet Coke, Root Beer, Coca-Cola, Pepsi and Sprite and comment will still be visible as comment context is regenerated to accommodate new members.
Case 2 :Removing access to existing dimension member for non admin user (Gary)
Remove access to the Coca-Cola dimension member for user Gary (non Admin), Gary will continue to view the comments placed with old access as again context would be regenerated with new members which he has access to.
Now Gary has access to Fanta, Diet Coke, Root Beer, Pepsi and Sprite and comment is visible
Datapoint comment behaviour with Data access control applied to parent node and the impact on the comments when new member added removed under a parent node
Similar to the data access control on the leaf node (as explained in the above section), if the data access control is applied on the parent node then by adding or remove new member under the parent node will give access to the new member to the non admin user as the data access has been applied at the parent node and the user will continue to see previously added comments.
for example:
Gary has access at the parent node level for Carbonated Drinks of product dimension and Carbonated Drinks has 5 members, Gary adds a comment, later new members has been added under Carbonated drink and now this has 7 members, still Gary will be able to view the comments which was added earlier. this happen as Gary will get access to all 7 members and comment context would be regenerated accordingly.
Enabling and disabling Data Access Control impact on the comments for Admin and Non Admin users.
DAC enable behaviour (DAC was disabled later it was enabled for a dimension).
- Comments added by Gary when DAC was not enabled will not be visible to Gary once DAC is enabled and Gary has been restricted to limited access. this is because the comments were added with full access and later Gary gets restricted access
- Example
- DAC is not enabled, Gary & Admin has full access to data, comments has been added by Gary and same comment is visible to both Gary and Admin.
- Example
- Now, enable DAC and give limited access to Gary, Comments added by Gary earlier will not be visible to Gary, as now Gary will have limited access to the data but Admin will continue to see the comment as Admin has full access which is same as the one when the comments was added.
- Gary is viewing the below table and since Gary has limited access hence the Gross Margin for California in 2015 is 13.61 as compared to the above image where the value was 53.95 comments are not visible to Gary
DAC disable behaviour (DAC was enabled, later it was disabled for a dimension).
- Comment has been added by Gary when DAC was enabled, this comment will not be visible to Gary once DAC is disabled and Gary has been full access; because earlier Gary had limited access and comment was associated with limited members, now since Gary has full Access the comments will not be visible by default but if Gary filters data explicitly to the limited member as earlier then he can see previously added comment
- Example:
- Comment added by Gary when DAC is enabled and Gross margin for California in 2015 is 13.61.
Later, DAC was disabled and Gary gets full access to the Gross margin for California in 2015 become 53.95 and the comments are not visible as comments were added with limited member access
Datapoint comment behaviour with multiple hierarchy
In model there possibility to have multiple hierarchy for the a dimension and there is possibility that two nodes can have same leaf node, for example in below table there is two hierarchy for overall drinks which are “Product type” and “Product Color”
In the below example Juice constitute of five drinks and same five drinks also available in product color hierarchy.
Datapoint comment privileges
In SAP Analytics cloud, you can control comment privileges at different level such as Role, Model and Story, for user to work on the datapoint comment within the story based on specific model they need to have respective commenting privileges at all the level and privileges denied at any level will ensure user will not be able to perform respective commenting operation.
Datapoint Comment accessible across stories
I have created a table based on model 1 where I can see table cell representing quantity sold for California and in another story having same data cell representing same value then the comment made on the cell will be visible in both story
Comment on a table with different visible dimensions but representing same datapoint
In the below list of table there are different representation within table (visible dimensions in the table) but they represent same datapoint so same comment would be visible in all three tables
- Table 1: California Gross Margin for product Juice
- Table 2: Juice Gross Margin for Product location California
- Table 3: Gross Margin for Juice for Location California and product Juice
4 Comments
