I have a problem when I try to autopopulate a people picker filed in infopath 2010 in a sharepoint 2010 form.
I am changing the edit form. In the edit form I want to autopopulate a people picker field (wich is based on a people column of the connected list) based upon another people picker field in the same list. In easy words I want to copy/past a value from one people picker field to another (in the edit form).
This does not work within the edit form. But it works in the new form. Has there anyone an idea for that.
I am not allowed to use coded solutions, only configuration (rules).
Thanks, Thomas
you should pass the 3 attributes/values of one people picker to another.
These are:
DisplayName
AccountId
AccountType
Now you can put a rule that when 1st people picker changes value, it will pass the 3 attributes to the 2nd people picker.
Related
I have a PowerApps app that has a field that is supposed to feed into a people picker column in SharePoint online.
I have a data card for "Manager Name" ,which is a people picker column in SharePoint, the card contains a combo box.
The Combo box contains this information which allows it to search Office 365 and return a list of users. I can then choose the user from the list.
This is the information for the data card which should feed into the SharePoint column
I'm not sure what I need to put into "default" and "update" fields which I think is where the issue is arising.
I am fairly new to PowerApps so sorry if this is an obvious question
Assuming your Combobox is working and you are getting the users just fine, you could trt the following:
Default: ThisItem.'Your Column Name'
Update:
{
'#odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
Claims:First(ComboBox4.SelectedItems).Claims,
DisplayName:First(ComboBox4.SelectedItems).DisplayName,
Email:First(ComboBox4.SelectedItems).Email
}
Now, you might need to change the combobox DefaultSelectedItems conditionally (if the FormMode is New, Edit or View)
DefaultSelectedItems
Table({
'#odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
Claims: ThisItem.'Your Column Name'.Claims,
DisplayName:ThisItem.'Your Column Name'.DisplayName,
Email:ThisItem.'Your Column Name'.Email
})
There is text filed in which "Author" name saved while submitting new form but while editing that form is there any way by which I can make it People picker and user can select the new name name and save the changes.
Unfortunately Naveen's answer's will not work for you.
The Client People Picker does not apply to SharePoint 2013 on-premise, except when writing a custom AddIn which you are not doing.
You also can't change the existing Text field of Author to be a people field directly as that is an illegal/invalid field type modification.
You will need to edit your existing field and rename it to something like AuthorOld/AuthorText. And then create a new field as a person field named Author.
However, it sounds like you're trying to let the user edit the field for who created the item. That field is locked for editing by end users. You can however, hide that field and just create a new person field with a default value of [Me] (this fills in the current users name when they create an item). Which will let you get the behavior it sounds like you're after :)
What my understanding is in SP Default edit form you have a Text Field to Save the User Value. Now you need to make that Text field as PeoplePicker Control.
You have 2 choice to done this.
1) Go with OOB. Make that Text field which is used to save the "Author" name as User Field. So it will be act as a PeoplePicker control in Both New/Edit Form.
2) Add Content Editor Webpart in the Edit Form. And make that Text Field as Client people picker.
Refer for
Client People Picker
Mark as answer if it helps.
I have a Survey list which has several questions, one of those is people picker field and the another one is single line of text field.
I need to hide a perticular question ( field ) based on login user. Requirement is as below
When the user logs in as admin
a. Display ‘people picker’ and should not allow user to pick his name from people picker.
b. Hide Single line of Text field.
When the user logs in as ‘Non-Admin’
a. Display ‘Single line of Text' field and default it to have the logged in user name (without domain name).
b. Hide ‘People picker’ control.
I am thinking that we can do it by placing javascript in content editor webpart and add it in newform.apx of survey list. Can anybody give me the proper approach to get it done?
Thanks in advance
You might like to try creating a custom field control, a differnet one for each field.
Javascript is fast and involves minimal deployment, but is fiddly and can be turned off.
Currently working with dropdown column in the moss 2007.
my question is
I created dropdown column in a list, it has 3 options. Suppose if option1 is selected then the new field (let say a text box) should pop up, if option2 is selected the another new field (say a dropdown should pop up) and similarly for option3. How to make these things show up when certain option in drop down selected? should I need to code for it? Educate me! Article would be a great help.
P.S->> Our organisation isn't so keen in working with infopath, infopath is out of option. Can I code in sharepoint designer itself???
This isn't possible using only SharePoint out-of-the-box (OOTB). It would require building a custom solution. You would need to create a custom field for each option, that checks the value of the choice field and determines whether to hide itself based on that.
I have a document with an attachment.The document is in edit mode but i want to restrict user to edit the attachment.User should be only able to open an attachment and should not be able to edit that attachment or Edit option should remain inactive.I am woking on client based application.If you have idea how to make Edit option inactive, then please share it with me.
Thanks Rupesh
I have not done any notes thick client work in more than a few years, but one way would be to have 2 subforms with the same richtext field. One gets an editable rt-field, and the other gets a computed-when-composed (same field name).
Put the subform in the base form as a computed subform. Base the formula on role, so you either get an editable field or non-editable field based on who you are.
I was thinking you could do this with a controlled section as well, but it's been too long to recall for me. I know the subforms would work.