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

TaxonomyPicker - Termset tree constructed incorrectly #199

pjwise opened this Issue Dec 10, 2018 · 1 comment


None yet
2 participants
Copy link

pjwise commented Dec 10, 2018


[ ] Enhancement
[x] Bug
[ ] Question


Please specify what version of the library you are using: [1.9.0]

Expected / Desired Behavior / Question

The taxonomy picker should correctly construct and display the tree structure of a termset.

Observed Behavior

The taxonomy picker places terms under an arbitrary parent causing the output to look different from the original termset structure.

See here that the term "Get Involved" lives under "Emergency" in the picker:

And "Human Resources" has no children:

However, in the termstore we can see that "Get Involved" lives under "Human Resources":

This relationship is also clear in the data returned from the request made by the taxonomy picker:

Steps to Reproduce

I tried a few times to reproduce this with standard terms to no avail. It may be that the tree reconstruction fails after a certain number of elements are inserted or it might break because the term is reused. However, the data it is pulling back in the example shows a clear parent-child connection between "Get Involved" and "Human Resources" with the correct guids.


This comment has been minimized.

Copy link

estruyf commented Jan 31, 2019

@pjwise I experienced another issue which might be similar to yours and I already implemented a fix for it. Would you be able to test out the latest beta and verify if this also fixes your issue?

More information about how you can test out a beta version can be found here:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.