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

group-header-remove-column-name has made me sad, please help #818

Open
JoeAyre opened this issue Jul 8, 2024 · 2 comments
Open

group-header-remove-column-name has made me sad, please help #818

JoeAyre opened this issue Jul 8, 2024 · 2 comments
Labels
🐞 Bug Issue with one of the samples

Comments

@JoeAyre
Copy link
Contributor

JoeAyre commented Jul 8, 2024

Sample (which sample are you having trouble with)

group-header-remove-column-name

What Should Happen

If a view is grouped by two columns, the group header should be removed for both columns that the view is being grouped by.

What Actually Happens

Whilst the group header is being removed for both columns, a most perculiar thing is being experienced. When the second level of grouping is expanded, all the nodes at that level acquire the same name, and this also happens at the first level of grouping. It's very odd. It is like a variable is set and all the nodes reference that variable instead of the raw data. I believe the "txtContent": "@group.fieldData.displayValue" part of the JSON is where the issue lies.

GroupedByJSONIssueVideo.mp4
@JoeAyre JoeAyre added the 🐞 Bug Issue with one of the samples label Jul 8, 2024
@tecchan1107
Copy link
Collaborator

Thank you for submitting this issue @JoeAyre ! I checked and was able to reproduce the same phenomenon in my environment.

However, I believe this is not a bug in the sample, but in Microsoft Lists. Therefore, I have created the following issue and reported it to Microsoft.
SharePoint/sp-dev-docs#9794

@JoeAyre
Copy link
Contributor Author

JoeAyre commented Jul 9, 2024

Thanks @tecchan1107 for going to the effort of reproducing the issue and writing up the bug report in the SharePoint area. Hopefully we get a resolution on this soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 Bug Issue with one of the samples
Projects
None yet
Development

No branches or pull requests

2 participants