Hi All! -- I have a perplexing issue, and was hoping someone might help.
- I have a "List Button" which launches a Visualforce Page.
- The Visualforce Page collects information on which Records the User selected in the List View, and then launches a Flow (using flow:interview)
- I'd love the flow to display using the Lightning style
- I added: LightningStylesheets="true" to the Visualforce Page, and it does indeed change the flow.... but only for the System Administrator
- When any other Profile uses the List Button -> to load the VF Page -> to Launch the Flow, the result for them is Classic styling.
From what I've read, it looks like lightningStylesheets="true" may still be in BETA, but the documentation seems to indicate that it should work with flow:interview.
The problem certainly presents as a Profile issue, but I can't find any Profile setting that would impact this 1 thing. The non-Admin profiles I'm testing with have "Lightning Experience User" = true, and "Hide Option to Switch to Salesforce Classic" = True.
Any thoughts would be apprecieated! Thanks!
Here is the VF Page:
Here is what the Admin sees when the flow runs:
Here is what non-admin Users see when the flow runs:
2 respostas
Salesforce Support was able to resolve my issue. I'm posting it here to help others that might come across this.
The issue was caused by "UserPreferencesLightningExperiencePreferred" field on the User record being set to false.
This field is normally changed when using the "Switch to Lightning Experience" or "Switch to Salesforce Classic" option, but for the profile I was using, the "Hide option to switch to Salesforce Classic" was enabled, so the User never "Switched" to lightning (they were force in to it) so the "UserPreferencesLightningExperiencePreferred" was never set to TRUE.
The Visualforce product team confirmed that the behavior I saw is expected when a user is in Lightning Experience but the UserPreferencesLightningExperiencePreferred field is set to false. Setting that field to true (using the Data Loader) resolved the issue for the User.
For what it's worth, here is a Known Issue (https://success.salesforce.com/issues_view?id=a1p300000008ej2AAA) that is somewhat similar to what I experienced.
Big thanks to Nick @ Salesforce, and the various support teams he collaborated with to figure this one out!
Dave