I am trying to add managed metadata column directly from the form. I keep getting a "Current User Has Insufficient Permissions to perform this operation." message. I am both a Site Collection Administrator and a group manager for the MMD termstore on the Site Collection I am working from.
Yes. All looks correct with the term set. Here is another observation...
Thanks for your question!
Unfortunately, this feature is not yet available in Nintex Forms for Office 365. However this feature is on our road map for Nintex Forms for Office 365. A feature request has already been created on our user voice site here:
Please add your comments to the user voice post so we can add visibility to the need for this feature!
I know that Managed Metadata is not yet available and is on the road map, however I was curious to know how people are currently managing the lack of it for their online forms.
For instance: I want my users to have a SP list which uses a list of all cities / countries to select from, hence from Term Store, and I also want them to have a nicer Forms with Nintex, but doing so will lose the selection within the list of cities/countries.
My idea would be for now to have a duplicate field [City_manual] which is a choice with the list of all cities (damn long, may reach limit!) and then a workflow to write the value of [City_manual] into [City] (termstore field).
then this approach allows me to use the Managed Metadata field when/if released later just by deleting the [City_manual] and showing the original field on the form.
Is that how you guys do in the interim or do you just ignore the Managed Metadata totally until there is actually one in Nintex Forms ?
I have the same question and I don't believe there are larger Nintex customers out there that aren't using Metadata columns in their Forms. Metadata columns and mapped to the People Term Group which set as default in the User Profile for most organisations. the bottom line is I won't be able to go beyond the current Trial of Office 365 Forms with my client, without some workaround ahead of when this feature is added to the product.
We recognise that the managed metadata control is important to your business processes and have begun the work on the control for Office365.
We will keep you updated on UserVoice.
I get this will need put through the dev and qa cycle. I have had to think of a workaround to get passed this so I can still use the cascading lookups.