Managed Metadata Fields in Office 365/SP Online Sandbox Solution
Hi, Developing Metadata fields is always a complicated case of the developers. My previous posts( Add Metadata Taxonomy Custom Field using Visual Studio ) I explained how we can create metadata site columns. In this post, I will target Office 365/SP online users who can only use sandbox solutions to update/create metadata fields. Reason why treditional solutions does not with Office 365 In practical scenario, Metadata service details like SSPID, Default term store etc keep on changing. I notice that the name of Metadata service of SharePoint Online keeps on updating after some updates. We all know that code in sandboxed solutions is being deprecated by Microsoft. But even if we were happy to use sandboxed code - in Office 365/SharePoint Online, we cannot use the Microsoft.SharePoint.Taxonomy namespace in server-side code anyway – the net result is that we are unable to “finish the job” in this way to ensure the field is correctly bound to the Term Store. This is a problem! Even wor...