#Lightning Performance1 discussing

Do you use managed packages built with Lightning Web Components? Your Salesforce users might be losing 30+ seconds every day on their initial record load due to a Salesforce known issue that needs to be better prioritized. 

Have you noticed how on some Lightning record pages, the initial load takes 30+ seconds and seems totally unexplainable? Then after that first load, it's fine for the rest of the day. 

Here's what makes this worse than it looks: it's not a one-time delay. Every individual user hits their own cold start, so if you have 50 users opening an affected record type each morning, that's 50 separate 30-60 second delays, every single day. The productivity cost scales directly with your user count. 

We spent weeks investigating this on our managed package pages with the managed package vendor before Salesforce support confirmed it's a platform-level known issue affecting Lightning pages with shared component subtrees, not something specific to any one vendor's code: 

Known Issue: Flexipage performance degradation on DynamicComponent

 (Reference ID: W-23284931) 

This known issue feels significantly underreported for how big the impact is. If you've written it off as your imagination, blamed it on a slow server day, assumed it'll just go away, or your users have just been complaining without ever filing a ticket, this is likely why. 

If you manage Lightning pages with complex or shared component structures and have noticed this pattern, please report the known issue above against your own org and ask your AM for a timeline of when the issue will be fixed. At a minimum, it just takes clicking a checkbox on the known issue. I am hoping more visibility on the known issue means more pressure on Salesforce to prioritize a fix. 

#Lightning Performance  #Lightning Web Components  #Installed Packages  #Salesforce Admin  #Salesforce

We recently allowed all users to switch between Lightning and Classic with the hopes of getting to all Lightning soon. Given the feedback from our users, including our C-Suite executives, that goal is in jeopardy. One comment was we can do better in spreadsheets or classic how is this an improvement?

1. When summing data on summary reports executives want the ability to see Totals Amount at the top of the screen that does not include lost deals. When the summary includes rows for lost deals for information the Sum includes those values unless we do a special formula. Since formulas are limited the question is why would the grand total include loses? The grand total is much more obvious at the top in Lightning so is drawing attention to the fact that losses are included. The executive’s comment was this is basic CRM you don’t add loses together with Wins or pipeline.
2. In Classic formula fields on reports did not show fx in front of the formula. Our executives want this off, but we have no control of that indicator. This is an example of Lightning being worse than classic in their perspective.
3. Formatting on reports is not sufficient.
   1. Once you set column width is does not appear to be saved permanently. Other users cannot see the same column width and the ones an individual saved reset at some point. The reset does not seem consistent so we haven’t figured out how it is happening. The column width should be saved on the system so that it can be shared on public reports.
   2. When you scrolled down in Classic the grouped column showed that value but as you scroll in Lightning the value goes away. You have no idea which group category you are viewing.
   3. You do have the ability to size columns but then the headers wording doesn’t word-wrap and you don’t know the full name unless you hover. This is an example of how a spreadsheet is better than Lightning.
4. MANY users have commented how much slower lightning is loading pages than classic. This is causing many users to not want to move to Lightning. I believe most of our users have fairly new machines with good amount of memory, so this should not be an issue with the machines.