[Alexander Bautz]

This solution has never been intended used with people pickers, but it might be possible to add this to a future release. Can you add an attachment with some screenshots so that I can see exactly what you experience?

Alexander

[Alexander Bautz]

This is now in place. Check out v2.105 and let me know how it works out.

Read the change log, and use the “help icon” on the viewFields section to learn how to use “replace”.

Alexander

[Alexander Bautz]

I’m sorry for the delay. I’ll look into this later tonight.

Alexander

[Alexander Bautz]

Hi,
Sorry for the delay. I think this one may be related to the bug that was fixed in v4.257 https://spjsblog.com/dffs/dffs-change-log/. Can you check to see if this was it?

Alexander

[Alexander Bautz]

You can create a rule that checks the group membership in a group, and then use a rule on the dropdown that uses the “And these rules are true” to verify that the group membership is OK.

Let me know how this works out.

Alexander

[Alexander Bautz]

I’m glad you figured it out.

Alexander

[Alexander Bautz]

Hi,
This is the complete setup for SPJS-Lookup where I have used the CAML in my previous post:

	var argObj = {
		"fieldToConvertToDropdown":["SPJSLookup1"],
		"optTextFieldInternalName":"Title",
		"listName":"Tasks",
		"listBaseUrl":"/DFFS",
		"sortFieldName":"Title",
		"filterObj":{
			"on":true,
			"folder":"",
			"CAML":"<Where><And><IsNotNull><FieldRef Name='Title' /></IsNotNull><Eq><FieldRef Name='AssignedTo' LookupId='TRUE' /><Value Type='User'>"+String(spjs.dffs.beforeProperties["Requester_ID"])+"</Value></Eq></And></Where><OrderBy><FieldRef Name='Title' Ascending='TRUE'/></OrderBy>", // Full CAML query. If used, the rest of the filterObj settings are disregarded
			"fin":"",
			"isLookup":false,
			"operator":"Eq",
			"filterVal":""
		},
		"dropDownDefaultvalue":"...",
		"addYouOwnValue":{
			"on":false,
			"linkText":"Write your own value"
		},
		"addToExternalList":{
			"on":true,
			"customFunction":null,
			"linkText":"Add new item",
			"saveNewItemText":"Save new item"
		},
		"debug":true
	};	
	spjs.lookup.init(argObj);

Regarding the people picker field name:
My people picker has FieldInternalName “Requester”, but the “beforeProperties” object has a separate property containing the ID of the person in the people picker. This is stored in the “Requester_ID” attribute. If your people picker is named “MyPeoplePickerField”, you must use “MyPeoplePickerField_ID”.

I hope this clarifies it a bit.

Alexander

[Alexander Bautz]

Hi,
Have you tested it? – I’m fairly sure this solution will remove duplicates so that only unique values show in the dropdown.

Alexander

[Alexander Bautz]

It’s hard to tell. Could there be some other code that interferes? If you have any third party code, try to disable it. If note, try to set up a new, fresh list to test it there.

Alexander

[Alexander Bautz]

The code looks OK. Are you 100% sure this is the CEWP code you use? Have you tried to add an alert to verify that this is the one?

Alexander

[Alexander Bautz]

Hi,
It looks like you have the wrong variable name. It is not

var spjs__spPageContextInfo = ...

but

_spPageContextInfo = ...

Alexander

[Alexander Bautz]

Sorry, but this is not possible with the autocomplete solution, so I’m afraid you will have to go with the stock people picker field for this one.

Alexander

[Alexander Bautz]

Hi,
The autocomplete reads the users from the user list in the site collection. My best bet for why the user does not appear is that the user have not yet signed in to the site (all users must sign in one time before they are written to the user list).

Could this be the issue?

I could add a “kill” switch to the autocomplete, but I cannot use it to add people to the user list in SharePoint.

Alexander

[Alexander Bautz]

You could use something like this: http://api.jquery.com/jquery.getscript/

Alexander

[Alexander Bautz]

Hi,
First, DFFS should not be added to the list view – only in NewForm, DispForm and EditForm. vLookup however must be added to the list view if you want the vLookup columns to render there.

The “missing” list tools can be made visible by clicking anywhere inside the “list view table” for the current list – no need to check the “select all”.

The tool you refer to is this: https://spjsblog.com/2012/01/12/bring-back-the-missing-list-tools-menu-in-list-view-with-multiple-webparts/

I have not tested this in SP2013.

Alexander

[Author]

Posts