Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: CommandBar Every button click returns the first item in Items table #513

Open
JediMasterFluff opened this issue Jan 21, 2025 · 1 comment
Labels
bug Something isn't working ⚠️ needs triage Has not been triaged by the team yet.

Comments

@JediMasterFluff
Copy link

Describe the bug
I am on the latest version of the creator kit and using the CommandBard v 1.1.39.

I have been using the kit for years, the CommandBar the most. Recently, regardless of what button I click, the Self.Selected record is always the first item in the Items table for the control. The buttons all render as I expect, but the select event always returns the same item.

This has rendered the component completely unusable.

To Reproduce
Steps to reproduce the behaviour:

  1. Insert Command Bar
  2. Assign the Items property to a table of items to display
  3. Update OnSelect to Notify($"Button Name: {Self.Selected.ItemDisplayName} | Button ItemKey: {Self.Selected.ItemKey}"
  4. See that the value returned on every button click is the same in the notification message

Expected behavior
The record of Self.Selected is the record assigned to the clicked button in the Items table.

Screenshots
See attached recording of issue.

Additional context

CommandBar.Selected.Item.Issue.mp4

Commandbar code.txt

I was seeing the same issue with the 1.1.34 version as well.

@JediMasterFluff JediMasterFluff added bug Something isn't working ⚠️ needs triage Has not been triaged by the team yet. labels Jan 21, 2025
@w1ngsss
Copy link

w1ngsss commented Feb 5, 2025

Could you please check the Fields property of the command bar and check if you have the ItemKey column selected as a field?

There has been a change to the behaviour of components a couple of weeks ago and setting the required column via Fields solves many of the issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ⚠️ needs triage Has not been triaged by the team yet.
Projects
None yet
Development

No branches or pull requests

2 participants