[Alexander Bautz]

Thank you for the feedback. Can you tell me how many fields of the following types you have in your form:

1. People pickers
2. Taxonomy fields / managed metadata

Any other “complex” fields?

Alexander

[Alexander Bautz]

I did actually not think of this initially, but I’ll add support for this as soon as I have sorted the current bugs in v4.25x.

Alexander

[Alexander Bautz]

I’m currently working to resolve these issues, but I have not been able to recreate the errors locally.

It would help if you could test this BETA, and the updated spjs-utility.js

Open the developer console (hit F12 > Console) and click on any error messages and posti the line where the error occurs here.

Also post the SharePoint version and which browser you use.

Alexander

[Alexander Bautz]

Hi,
The problem is that the field is actually a single line of text field (but the input is hidden), and the script generates a dropdown in its place. This means that using “setFieldValue” will set the single line of text field because the script “knows” this field is of type single line of text. You must therefore add another line of code to find the select and set its value “manually”.

Alexander

[Alexander Bautz]

Sorry, I have no such solution. You should look at for example ShareGate.

Alexander

[Alexander Bautz]

Hi,
Yes this is currently a requirement. I have somehow forgot to put this in the manual, but it is mentioned in this post: https://spjsblog.com/2012/02/12/list-view-preview-item-on-hover-sharepoint-2010/

No wonder you did not find it though. I’ll make a note so I remember to update the manual.

Alexander

[Alexander Bautz]

You are right, I have updated the change log. Please note that I have fixed one bug in frontend v4.251.

Alexander

[Alexander Bautz]

Thank you for the feedback – this will be fixed in the upcoming release.

Alexander

[Alexander Bautz]

I will add the ability to have the “customProp” as an array of FieldInternalNames in the next release of spjs-utility.js.

In the meantime, you can modify your current version by changing this:

if(customProp !== undefined){
	arrOfFields.push(customProp);
}

like this:

if(customProp !== undefined){
	if(spjs.$.isArray(customProp)){
		spjs.$.each(customProp,function(i,p){
			arrOfFields.push(p);
		});
	}else{
		arrOfFields.push(customProp);
	}
}

Alexander

[Alexander Bautz]

Hi,
I do not have a ready to use code example, but will keep this request in mind and see what I can do. I am however busy working on bringing the latest DFFS version out of BETA, so I cannot promise anything.

Alexander

[Alexander Bautz]

Hi,
Sorry for the delay. Currently it does not support anonymous access. I will try to add this to the next release, but this has been delayed due to work on DFFS.

Alexander

[Alexander Bautz]

I have updated the BETA of the frontend script to v2.104. You find the change log here: https://spjsblog.com/vlookup-for-sharepoint/vlookup-change-log/

Alexander

[Alexander Bautz]

Strange, I have not seen this before. Is it possible that you have some code that interferes with the date picker?

Alexander

[Alexander Bautz]

Hi, I have seen this happen if a user double clicks on the calendar icon. Does the calendar go away if you click the icon again?
Alexander

[Alexander Bautz]

Hi,
Thank you for the feedback – I will fix this error message in the production release of DFFS v4.210.

Alexander

[Author]

Posts