New answers tagged

0

I stumbled across this thread while having this same problem. However, the original solution shown in this original thread did not work for me using a Sharepoint 2013. After a lot of trial and error, I was able to make it work by: 1. Making the multiselect column a lookup column and make a separate list for all the selections 2. Create one entry in ...


1

I'm now told over at MSDN that this is not possible OOTB. https://social.msdn.microsoft.com/Forums/sharepoint/en-US/511f5495-07af-457c-aa8b-bc45910cdcf1/using-spd-workflow-to-set-approval-workflow-task-outcome?forum=sharepointcustomization


0

Viewing with console developement browser, I find the source problem : SetDisabledOnControl function is unknown. This post indicates the source problem is an UC update. But I can't test the proposition on this post to validate it. I think it's dangerous to edit a forms.js file on a PROD server. The solution is to upgrade this site collection to user ...


0

You need to check if the user with whom you try to add value to choice field is having "Contribute" access on the list/library in which this field has been added.


1

This feature is not available as out of the box (you need to customize it with visual web part or InfoPath form) Regarding switching from check box to drop down Go to List Settings > In the column settings > Select drop down instead check box


0

You can use JQuery for this purpose. $(document).ready(function () { $("#idoftheTableElementContainer input").each(function () { $(this).change(function () { //label next to checkbox holds the value. if ($(this).next().val() == "random value") { $("#idofbutton").click(); } }); });...


0

Looks like it's a bug, but you can use: Add-SPOField -InternalName "DD" -DisplayName "dd" -Group "D" -Type Choice -Choices @("111","222") https://github.com/OfficeDev/PnP/issues/255


0

Your question doesn't give much details on your environment or how the list/columns where originally created, so I will have to guess. As you may have guess, there is no out-of-box functionality to allow such field type change (as least afaik), so you will have to resort to a custom "migration". There are two opposite cases that we should consider: Option ...



Top 50 recent answers are included