[Alexander Bautz]

Hi,
Thanks for the feedback. I’m not sure I understand. The default behavior is that the vLookup for the current field collapses and you can continuer configuring another vLookup column or DFFS. What exactly are you seeing after the save?

Any errors in the developer console? (hit F12 > Console).

Alexander

[Alexander Bautz]

Hi,
Add this code to the Custom JS section in the Misc tab. Change the FieldInternalNames in the “arr” to match your field names:

(function(){
	var arr, chk; 
	arr = [
		{"trigger":"YesNoFieldNr1","comment":"YesNoFieldNr1_comment"},
		{"trigger":"YesNoFieldNr2","comment":"YesNoFieldNr2_comment"},
		{"trigger":"YesNoFieldNr3","comment":"YesNoFieldNr3_comment"}
	];
	$.each(arr,function(i,o){
		// Click
		chk = $(spjs.dffs.fields[o.trigger]).find("input:checkbox");
		chk.click(function(){
			toggle_requiredByYesNo($(this),o)
		});
		// Load
		toggle_requiredByYesNo(chk,o);
	});
})();

function toggle_requiredByYesNo(elm,o){
	if(elm.prop("checked")){
		spjs.dffs.flag_Mandatory([o.comment]);	
	}else{
		spjs.dffs.clear_Mandatory([o.comment]);	
	}
}

Alexander

[Alexander Bautz]

Hi,
This is added in v2.0 of vLookup.

Alexander

[Alexander Bautz]

Hi,
The new v2.0 of vLookup sets a class “spjshidden” to the field, and if you update DFFS_frontend.css to v4.04 the hidden fields will be “respected” by DFFS.

Please note that v2.0 of vLooup must be tested in your environment before you can switch over.

Alexander

[Alexander Bautz]

I guess you need to add a custom JS function in the Misc tab and trigger this from a rule.

Let me know if you need help with an example.

Alexander

[Alexander Bautz]

I’m sorry, but this is a bit tricky to answer. If you can add a screenshot of the DispForm you are trying to print I might be able to help.

My best guess would be to add some CSS that triggers on print to make the form fit on the printout. This is the format of the CSS code you will want to use (contents is only an example):

@media print {
    div {
        font-size: 20px;
        color: red;
    }
}

Alexander

[Alexander Bautz]

There is currently not a “between” operator, but you can try setting up two rules – one for “is less than” and one for “is greater than”. For the first you set no “actions” and for the second one you add the previous rule index in the field “And these indexes are true”.

Alexander

[Alexander Bautz]

This sounds strange. Can you verify that you can set the value in a text field? – are you sure this rule is triggered?

Alexander

[Alexander Bautz]

There is not a definitive limit, but 100 rules will take its toll on the browser. I have not tried this myself though.

Your specific requirement would be better solved with a few lines of custom JS. This will require a list of the fields you want to apply this rule to, and a corresponding list of comment fields to make required.

I’ll try to whip up an example during the weekend.

Alexander

[Alexander Bautz]

Hi,
The “hide in child NewForm” option was initially intended for NewForms where you did not have any other code to handle the hiding of the field. DFFS ignores this setting and will make this field visible again if the field is included in a tab or made visible by a rule.

I’ll see what I can do to make DFFS respect this setting.

Alexander

[Alexander Bautz]

Hi,
It should be enough to have the variable “spjs_dffs_license” (or “spjs_license”) in the page where you configure DFFS.

Alexander

[Alexander Bautz]

Hi,
This is not built in functionality as JavaScript cannot send an email on it’s own. I think your easiest solution is to create a workflow that starts when a field is set to a certain value / changed, and then use a DFFS rule to set this field based on a condition.

Another option is to use this solution: https://spjsblog.com/2010/06/16/send-email-with-javascript-with-the-help-of-a-workflow-in-a-dedicated-send-email-list/ and call a function from the custom js section in the misc tab with a rule in DFFS.

Alexander

[Alexander Bautz]

Yes, this should be straight forward – did you test it?

Alexander

[Alexander Bautz]

Hi,
I’m not sure I can do anything about this as by default there is a redirect / refresh when deleting an item or closing a dialog. If you do not have a “Source=SomeURL” in the URL, you will be redirected back to the default list view of the list you deleted the item in.

You might be able to “hack it”, but this would take some custom code.

As a start you can look at this code that hijacks the built in delete function in SP2013 and possibly SP2010? (add it to the DispForm of the item you want to delete):

/* must refer jQuery and spjs-utility.js scripts */
DeleteItemConfirmation = function(){
if(confirm("Are you sure you want to delete this item?")){
var res = spjs_deleteItem({"listName":_spPageContextInfo.pageListId,"id":GetUrlKeyValue("ID")});
if(res.success){
if(GetUrlKeyValue("IsDlg")==="1"){
alert("Item deleted successfully");
window.frameElement.commitPopup(); // < this code will make the parent page refresh...
}else{
alert("add a redirect here..:");
}
}else{
alert("Delete failed with this message:\n"+res.errorText);
}
}
}

Alexander

[Alexander Bautz]

Hi,
I have released DFFS frontend v4.103 – look at the change log here: https://spjsblog.com/dffs/dffs-change-log/

This relase adds a class “dffs_required” to the

of all required fields. You can use this to add your custom style to required fields. Look at the bottom of the file DFFS_frontend.css for an example.

Alexander

[Author]

Posts