TaxonomyPicker - Termset tree constructed incorrectly

[pjwise]

Category

[ ] Enhancement
[x] Bug
[ ] Question

Version

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.

[estruyf]

@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: https://sharepoint.github.io/sp-dev-fx-controls-react/beta/

[AJIXuMuK]

@pjwise - is it still an issue on the latest version of the library?

[ghost]

This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within next 7 days of this comment. Thank you for your contributions to SharePoint Developer activities.

[ghost]

Closing issue due no response from original author. If this issue is still occurring, please open a new issue with additional details. Notice that if you have included another related issue as additional comment on this, please open that also as separate issue, so that we can track it independently.