Einstein Analytics - Login as Community User doesn't pass correct user context to apply Security Predicate on dataset

Einstein Analytics - Login as Community User doesn't pass correct user context to apply Security Predicate on dataset

Analytics , Communities

Last updated 2019-05-04 ·Reference W-5435728 ·Reported By 34 users

Fixed - Summer '19

Einstein Analytics doesn't recognize the "Login As Community User" method which means community users information is not passed to Einstein Analytics.

One consequence of this behavior is that Security Predicates on Datasets referenced in the embedded Dashboard apply row-level security based on the Admin who logged in as the community user.

Another consequence is that Admin users without Analytics Permission Set License Assignments will get an error when trying to view embedded Einstein Community Dashboards using "Login As Community User" with a Community User who does have an Analytics Permission Set License Assignment. In this scenario the Admin user would see an error saying “This feature is not currently enabled for this user” even though the Admin is logged-in as a Community User with an Analytics Permission Set License Assignment.

1. Create an Einstein Dashboard which references at least one dataset that has a security predicate.
2. Ensure the security predicate contains the dollar symbol to signify the logged in user similar to this: 'OwnerId' == "$User.Id"
3. Embed the Einstein Dashboard in a Community page.
4. Navigate to a Contact record for a community user.
5. Click "Login In As Community User" on the contact record to access the Community.
6. Navigate to the Community page with the embedded dashboard.
7. Row-level security is applied as the Admin (not the community user).

Directly logging in as a Community User will allow the Einstein Analytics environment to load with the correct session information and permit the Security Predicate to operate in the correct context.

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP14 AP15 AP20 AP21 AP22 AP28 CS1 CS2 CS3 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS110 CS11 CS116 CS12 CS137 CS138 CS13 CS14 CS15 CS152 CS151 CS16 CS17 CS18 CS19 CS20 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS29 CS30 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS50 CS51 CS52 CS53 CS54 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS71 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS82 CS83 CS84 CS85 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS93 CS94 CS95 CS96 CS97 CS98 CS99 EU7 EU8 EU10 EU12 EU13 EU14 EU15 EU16 EU17 EU18 EU19 EU25 EU26 EU29 EU30 NA104 NA100 NA101 NA103 NA102 NA105 NA129 NA130 NA132 NA131 NA146 NA154 NA155 NA196 NA21 NA32 NA33 NA37 NA39 NA40 NA42 NA44 NA45 NA46 NA47 NA49 NA50 NA51 NA52 NA53 NA54 NA56 NA57 NA58 NA59 NA60 NA61 NA62 NA63 NA64 NA65 NA66 NA67 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA78 NA79 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.