I have a quickaction that is overridden by a lightning component. Apparently lightning caches the component or something because calling the quick action from two different records brings up the same component with the same data; a manual refresh will then correct the issue. Is there anyway to change this behavior rather than hacking something out ?


You can disable the cache in the setup (see how to in the answer here), although it'll affect performance for all users using lightning.

Not ideal, but can't think of a better solution.

| improve this answer | |
  • Thanks I have seen that. That is for components under development, which seems like annoying but somewhat expected behavior. My problem is that the exact same initialized component is called by a quick action in two entirely seperate records – SallyRothroat Apr 1 '19 at 21:50
  • this can't be expected behavior. – SallyRothroat Apr 1 '19 at 21:50
  • And in fact, that setting is unchecked in the org – SallyRothroat Apr 1 '19 at 21:52
  • I hear, strange behavior. Figured if you hadn't tried this setting, it was worth a shot – Brian Miller Apr 1 '19 at 22:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.