Forum Discussion
SPFx Bing Maps Callback Issue
Hi Adam Reid ,
I think (but I'm not sure), there is some conflicts because of oob Bing webpart and Bing Maps Web Control use same sdk calls and same approach, and they live in the same page context.
What about use instead Isolated webpart? could it be a workaround?
From page point of view, it is an iFrame, and it could solve your problems.
The scope of isolated webpart is another (security API) but you can easly try.
I"f you're upgrading an existing SharePoint Framework project to v1.8.0 and want to use the isolated permissions capability, you can do it, by setting in the config/package-solution.json file, the isDomainIsolated property to true. You should ensure, that your project contains only web parts."
Cheers,
Federico
- Adam ReidNov 05, 2019Copper ContributorHi Federico, thanks for your reply. I'll have a closer look at the isolated webpart. Assume I'll have to implement my own security as I'll loose access to SharePoint http client? I'll weigh up the pros and cons and if I get anywhere with it I'll report back.
Cheers, Adam- Nov 07, 2019
Hi Adam Reid ,
sorry you don't tag me, I don't see your reply 🙂
What do yo mean about "Assume I'll have to implement my own security as I'll loose access to SharePoint http client?"
While using isolated webpart, you have already access to SharePoint context, and every other context you need. Isolated webpart it is simply an iFrame in another dns domain, but always on SharePoint context. You need to pay attention to UI approach, because your webpart live inside an iFrame, so you could meet some trouble.
Cheers,
Federico
- Adam ReidNov 11, 2019Copper Contributor
Sorry FedericoPorceddu82 🙂
Thanks for clarifying this...I was under the impression I would lose the SharePoint context inside the iFrame but it's good to know this isn't the case.
You mention I could encounter some issues; is there anything obvious I should be aware of?
Thanks again, Adam.