Jim Love

Does anyone know if this issue is being picked up by MSFT or is it waiting to be fixed by the community?

@nikithauc No worries, would be good to know if this is on the timeline to be implemented or not. Any solution that uses this SDK to communicate to MS Graph...

> With the new module https://pnp.github.io/powershell/ getting out in January 2021. I feel that this bug will never be fixed. > It's also very annoying that I cannot find ANY...

@tseward I had this same issue and was able to resolve it for now by manually installing 3.23 into Automation account.

@evlo What version are you using? I forgot about this issue, and just tried to reproduce it with 3.23 and it works fine now. EDIT: Forgot to Include IDs. Yep,...

@alexabramkin What about when you want to include the Term ID too?

@alexabramkin Yep, see my original post at the top here, you include the ID when you export. [Export-PnPTaxonomy](https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/export-pnptaxonomy?view=sharepoint-ps)

@alexabramkin Yep that's the workaround I ended up using. I swear I saw a PR into PnP Sites Core (and PnPCore) that fixed this, however - but I can't find...

Looks like this PR would fix that, but it looks like this repo is unmaintained now... https://github.com/StephenChou1017/react-big-scheduler/pull/187

Yeah we've noticed the same thing. Does 3.6 require a newer version of spfx? Should this be detailed in the docs? EDIT: Hackaround - just pass `this.context as any`, bypassing...