SPFx on a Team Site Homepage Cannot Get Taxonomy Data
Hi, I have an SPFx webpart and an SPFx extensions that getting data from Taxonomy Term Store. Both of them are working well on all pages (Site Content page, Library page, Site page, etc.) except on a Team Site Homepage. I've tried several approaches to get the Taxonomy data in the SPFx code: Add the references to the SharePoint JSOM in the config.json (https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/basics/add-an-external-library) Load SharePoint JSOM in the code (following example from Microsoft's repo: https://github.com/SharePoint/sp-dev-fx-webparts/blob/dev/samples/knockout-taxonomy/src/webparts/termSetRequester/data-helpers/DataHelperSP.ts, even the webpart example doesn't work on a Team Site Homepage) Both of them couldn't get taxonomy data on a Team Site homepage. It's failed on context.executeQueryAsync(...). Is there anyone that has done this before? Or has any workaround idea for this situation? ThanksHow would you build a custom solution based on the following requirements?
Environment: SharePoint 2013/2016 on-premise environment Requirements: Custom List form which needs to retrieve information based on filled inputs during edit > not after saving The information needs to be retrieved via Web Services from other internal applications > the authentication against the already present Web Services happens via Certificate Authentication and cannot be done client side Only users that have already access to the SharePoint site where the list with the custom form resides should have access to the functions to call the web services via custom form My approach would be to create a custom Site or Application Page with code behind with WebMehtods that can be executed client side via JSOM. Is this still the way to go or are there other more modern approach to implement such solutions? I'm aware of the client-side solutions that can be build but we're not able to call the present web services from client-side and we don't want to build new web services that themselves calls the present one because doing thins we'll need to implement a whole new solutions which handels authentication too. Thank you for your answers already in advance. I'm excited about your feedback ;-) Kind regards, Fabrizio
