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

DynamicForm - AnchorId of TaxonomyField gets ignored and the whole tree is rendered #1310

Closed
SmarterJB opened this issue Sep 13, 2022 · 1 comment
Labels
status:fixed-next-drop Issue will be fixed in upcoming release.
Milestone

Comments

@SmarterJB
Copy link
Contributor

Category

[ ] Enhancement

[x ] Bug

[ ] Question

Version

Please specify what version of the library you are using: 3.10.0

Expected / Desired Behavior / Question

If I set the anchor in a taxonomy field correctly, the dynamic form should not display all terms from the termset, but instead only the ones from the anchor down, as seen in the screenshot of the standard modern edit form of sharepoint. Here the term "process" was selected to be the anchor of the field.

image

Observed Behavior

The dynamic form displays the whole taxonomy tree from the termset as seen in the screenshot below. The term on the top of the tree should be the one named "process" as seen in the screenshot above.

image

Steps to Reproduce

Create a document library with a taxonomy field, set the anchor to something lower than the termset, and then open the dynamic form in this library, you can see that it will not use the correct anchor.

I will look into this and will try to create a PR for this issue myself!

Thanks!

@ghost
Copy link

ghost commented Sep 13, 2022

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@ghost ghost added the Needs: Triage 🔍 label Sep 13, 2022
@AJIXuMuK AJIXuMuK added status:fixed-next-drop Issue will be fixed in upcoming release. and removed Needs: Triage 🔍 labels Nov 16, 2022
@AJIXuMuK AJIXuMuK added this to the 3.12.0 milestone Nov 16, 2022
@AJIXuMuK AJIXuMuK mentioned this issue Nov 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:fixed-next-drop Issue will be fixed in upcoming release.
Projects
None yet
Development

No branches or pull requests

2 participants