[Alexander Bautz]

Hi,
This is currently not added to DFFS, but I have had other requests. This is a workaround you can use.

Add a function like this to the “Custom JS”

function appendHistory(){
	var history = $("#dffs_Textarea1").find("td.ms-formbody div.dffs_tdWrap div").has("a").html();
	$("#dffs_Textarea1").find("td.dffs-readonly-inner div.dffs_tdWrap").append("<div style='margin:2px;padding:3px;border:2px silver dashed;background-color:#ffffff;'>"+history+"</div>");
}

You must change “Textarea1” to your own FieldInternalName.

Then add a call to this function on the rule that sets the field read only (in the “Run these functions” field).

Let me know how this works out.

Alexander

[Alexander Bautz]

Hi,
Sorry, but DFFS (and vLookup) cannot read from SQL. You should be able to use a BCS if you add a column “ID” (unique number) to the data source.

There is no grid view to edit the vLookup data in, but this is only a view. Can you go to the list the data is pulled form and edit it in datasheet view there?

Alexander

[Alexander Bautz]

Try

<a href='{0}'>{1}</a>

Where column index 0 is the URL and index 1 is the text you want to show on the URL.

Alexander

[Alexander Bautz]

Hi,
I can make a modification to vLookup to enable “sum” of number columns. I’ll look at it this weekend and see what I can come up with.

Alexander

[Alexander Bautz]

Hi,
Sorry, but this is currently not possible.

Alexander

[Alexander Bautz]

Hi,
I have updates the description for the “Initially hidden fields” in the Misc tab earlier today (v4.256) as I simply forgot to change the description when I changed the functionality in v4.200.

If you look at the change log for v4.200 you see that this is effectively hiding the fields “permanently”, and to unhide it, you will have to use a custom function to remove the class “spjshidden”.

In most cases, you can change the trigger for example to [Applicable choice field] is NOT equal to [Applicable] > show the field. This will hide the field if you select “Applicable”.

Hope this helps,
Alexander

[Alexander Bautz]

Hi,
Hopefully, this code example will provide a working solution. Add the below code to the Custom JS, or the CEWP for the DFFS frontend.

Please note that you must change the FieldInternalName the function is called with in the bottom line, and you must change the parameters in “spjs.lookup.init” in the “fill” function in the top.

Alexander

var spjs_lookup_ppTrigger = {
	"fill":function(fin){
		var ppID = spjs_lookup_ppTrigger.getSelectedPeoplePickerID(fin);
		if(ppID !== false){
			spjs.lookup.init({
				"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'>"+ppID+"</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":false
			});
		}
	},
	"data":{
		"pp":{}
	},
	"init":function(fin){
		setInterval(function(){
			var a = spjs_lookup_ppTrigger.ppChanged(fin);
			if(a){		
				spjs_lookup_ppTrigger.fill(fin);
			}
		},2500);
	},
	"ppChanged":function(fin){
		var a = spjs.utility.getFieldValue({
			"fin":fin,
			"key":"loginName"
		}), b = false;
		if(spjs_lookup_ppTrigger.data.pp[fin] !== String(a[0])){
			spjs_lookup_ppTrigger.data.pp[fin] = String(a[0]);
			b = true;
		}
		return b;
	},	
	"getSelectedPeoplePickerID":function(fin){
		var a, b, c = false;
		a = spjs.utility.getFieldValue({
			"fin":fin,
			"key":"loginName"
		});
		if(a.length > 0){		
			b = spjs.utility.userInfo(a[0]);
			c = b.ID;	
		}
		return c;
	}
};

spjs_lookup_ppTrigger.init("PeoplePicker2");

[Alexander Bautz]

Hi,
It seems I have mistakingly assumed that the people picker was filled when the form loaded, and not being set manually in the form.

Can you confirm that the picker is set by the user?

If so, how do you plan to “fill” the dropdown? – by a button, or by “change” of the PP?

Alexander

[Alexander Bautz]

Sorry for the delay – I have had quite a lot of backlog on emails. I have looked at your code snippet above, and it seems that you have not changed the fieldinternalname to match the one you use. In my example, I used “Requester”, but this must be changed to the actual field you want to pull the information from.

Alexander

[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

[Author]

Posts