I'm encountering an unexpected behavior in a Salesforce LWC component, and I'm not sure if it's a bug or an issue with my code. Here's the scenario I'm observing:
Scenario:
1 - Page loads user is on "Tab 1"
2 - User clicks "Current Tab"
Console.log:
this.selection = []
this.getStateStepFilter = ['item1', 'item2', 'item3', 'item4'] // Unexpected, should be []
3 - User selects Item 1 and click "Update": works nice
this.selection = ['item1']
this.getStateStepFilter = ['item1']
4 - User clicks on "Tab 2"
5 - User clicks back on "Current Tab"
this.selection = ['item1', 'item2', 'item3', 'item4'] // Unexpected, should be ['item1']
this.getStateStepFilter = ['item1', 'item2', 'item3', 'item4'] // Unexpected, should be ['item1']
-- End
Additionally, when refreshing the page, the values seem to be set inconsistently.
Questions:
Is this a known Salesforce bug? Could this be an issue with my code?
Has anyone else experienced similar behavior with Salesforce tab components?
Full post here: https://salesforce.stackexchange.com/questions/424214/inconsistent-behavior-in-salesforce-lwc-hierarchy-tree-grid-selection-and-state
I'm working on a LWC Dashboard Analytics component - https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_lwc_in_db.meta/bi_dev_guide_lwc_in_db/bi_lwc_in_db_reference.htm
I'm encountering an unexpected behavior in a Salesforce LWC component, and I'm not sure if it's a bug or an issue with my code. Here's the scenario I'm observing:
Scenario:
1 - Page loads user is on "Tab 1"
2 - User clicks "Current Tab"
Console.log:
this.selection = []
this.getStateStepFilter = ['item1', 'item2', 'item3', 'item4'] // Unexpected, should be []
3 - User selects Item 1 and click "Update": works nice
this.selection = ['item1']
this.getStateStepFilter = ['item1']
4 - User clicks on "Tab 2"
5 - User clicks back on "Current Tab"
this.selection = ['item1', 'item2', 'item3', 'item4'] // Unexpected, should be ['item1']
this.getStateStepFilter = ['item1', 'item2', 'item3', 'item4'] // Unexpected, should be ['item1']
-- End
Additionally, when refreshing the page, the values seem to be set inconsistently.
Questions:
Is this a known Salesforce bug? Could this be an issue with my code? Has anyone else experienced similar behavior with Salesforce tab components?
XML