(This answer suggests an approach where the application event propagation is stopped at the container, but in this case I don't have control over the container.)Īpplication-level events certainly are what Salesforce recommends for the use case of components that will be "App Builder siblings" and need to talk to one another. ![]() Is there a way to limit the scope of an application event in this Lightning App Builder context? Is there a pattern I can implement to separate out the events? Is there a better way to get the components to interact? This screen shot illustrates the situation: there are multiple instances of the same Lightning App Builder page (IN-17-000299, IN-17-000298, IN-17-000297) on the screen at once and they each respond to each others events which is not what I want: console navigation is used), all instances respond to an event from any instance. Yes, firing and handling application events works fine when there is a single instance on the screen, but when there is more than one instance (e.g. ![]() This question has already been asked in Lightning Events in Lightning Page Context, but the suggested use of application events isn't working for me. These components interact: when a user clicks on a button in one component I need another component to react. ![]() I have a set of Lightning Components that I want to allow customers to assemble in different layouts and combinations inside the Lightning App Builder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |