Personalized Information Links are essentially our approach to row level security. Most importantly, they're simple to implement and manage. Check out how to create them.
Hi Pavan, Sorry, I thought I had translated in the audio. Yes, the name of the column opolyakov is not valid, but I don't know why it would think that is the name of the column. Those are Entity and Userid.
I think these are the screenshots you are asking for.
|Teacher Table table screenshot.PNG||77.62 KB|
|Lookup Info Link Screenshot.PNG||59.3 KB|
|Teacher Roster Info Link table screenshot.PNG||66.94 KB|
|Lookup table screenshot.PNG||42.89 KB|
I am trying to do a nested set of look up tables and follow this example. In one lookup table, I would like to assign a User Group to a School. In another lookup table, I would like to assign a teacher to a User Group. This way, it avoids having multiple entries for each of my usernames when narrowing the row level security if a teacher belongs to multiple schools.
In the video, what do I use for the expression to replace %=(Current_User)?
Perhaps poorly named - that is User Group in the Spotfire sense of the word, but rather just that the name of the column that joins the two lookup tables. The idea was to have a list of usernames each assigned to a group and a group each assigned to an entity. That way, if a user belonged to multiple entities, I didn't need to take up multiple lines for them in the one lookup table. That would be signified by the group they were assigned to.
I'm experimenting with two joins - one for group to group and the other from entity to entity. I'm just not sure where to put filter to current user statement.