[Alexander Bautz]

Hi,
I’m not aware of this issue. I have a few questions:

1. Is this the new BETA, or is it v4.200?
2. Can you give me some details on browser, SharePoint version etc?
3. Does it happen for all forms, or only some?
4. Any errors in the developer console (hit F12 > Console)?

Alexander

[Alexander Bautz]

Hi David,
Thank you for testing. I have a few quesions.
1: What kind of field is “Volume (Last 12 Months) and what trigger did you use to set it read only?

2: Did the field “English Approval – Writer” have a value that did not show up when set to read only? If so, what trigger did you use to set it read only?

3: Regarding boolean fields in DispForm – are you 100% sure you used the new version in the frontend?

Info regarding comparing dates: This change will use the full date including hours and minutes when comparing date values from two different fields – using one date col in the “If this trigger” field, and another date col in “This value” field – doing a compare using less than or greater than.

Alexander

[Alexander Bautz]

Thank you for the feedback.

Alexander

[Alexander Bautz]

I’m glad you figured it out.

Alexander

[Alexander Bautz]

Hi,
Add this code to your Custom JS section:

$("#dffs_POType select, #dffs_NumberPOLines select").change(function(){
	showFieldsByPOType();
});

function showFieldsByPOType(){
	var arr, a, b, ticker = 1;
	// Hide all
	while(ticker <= 10){			
		$("#sbs_OuterTR_"+ticker).hide();
		ticker +=1;
	}
	ticker = 1;
	a = $("#dffs_PODetails select").val();
	b = $("#dffs_NumberOfPOLines select").val();
	if(a !== "" && b !== ""){
		while(ticker <= b){			
			$("#sbs_OuterTR_"+ticker).show();
			if(a === "Service"){
				$("#sbs_Field_GLAccount"+ticker).hide();
				$("#sbs_Field_WBSSAPCode"+ticker).hide();
				$("#sbs_Field_CostCenter"+ticker).hide();
			}else{
				$("#sbs_Field_GLAccount"+ticker).show();
				$("#sbs_Field_WBSSAPCode"+ticker).show();
				$("#sbs_Field_CostCenter"+ticker).show();
			}
			ticker +=1;
		}
	}
}

You must verify that “POType”, “NumberPOLines” are the correct names. Also check that “GLAccount”, “WBSSAPCode” and “CostCenter” are the right *prefix* for your fields as the script appends 1-10.

In the tab where you have the PO lines, your side-by-side index must be from 1-10 for the side-by-side groups of fields as the code hides the entire line and not the individual fields.

You must also add “showFieldsByPOType” as “Click function name” for the tab where you display the PO lines.

PS: When using F12 to debug the code it will take a long time to render. This speeds up a lot if you close the developer console.

Hope this helps you on the way, and let me know if something is unclear.
Alexander

[Alexander Bautz]

It looks like you have a bit much going on here. This is a scenario where you would be better off creating a custom function that triggers on the change event on the trigger fields. If you can describe the basic logic you are trying to make, I can make a code example you can use as a starting point.

Alexander

[Alexander Bautz]

Try turning on the “Debug rules” option in the rules tab and look in the output for any rules looping.

Do you have a lot of rules configured for these triggers? Sometimes you are better off with a custom function if it requires a lot of “logic” to get to your goal.

Alexander

[Alexander Bautz]

Hi,
Which version of DFFS are you using? Can you add a screenshot of the rule you use to show these extra fields?

Alexander

[Alexander Bautz]

Hi,
Yes, DFFS works only with unmodified, out of the box forms, but your suggested approach should work. Let me know if you have further questions.

Alexander

[Alexander Bautz]

Hi,
This sounds strange. Can you add some screenshots and more details on the DFFS setup?

Alexander

[Alexander Bautz]

Hi,
You can do this by opening your NewForm like this:

http://www.contoso.com/Lists/TestList/NewForm.aspx?Source=/Lists/TestList/NewForm.aspx

Alexander

[Alexander Bautz]

Hi,
You might be better off using a calculated column like this:

=YEAR([Start Time])&""

Set the output to “single line of text” and please note the &”” at the end – this is to force the output as text and not a number.

Alexander

[Alexander Bautz]

Hi,
The field type mentioned is not supported in the function “setFieldValue”, but you can set it like this in the Custom JS section in the Misc tab like this:

$(spjs.dffs.fields["fAllDayEvent"]).find("input").prop("checked","checked");

Hope this helps,
Alexander

[Alexander Bautz]

Hi,
We have sorted this out by email, but for others experiencing the same:

As you have found, this behavior occurs when you have not configured the form with DFFS yet, and therefore no configuration is found. The overlay will time out with “this took forever”, but you can scroll down to the bottom of the form to find the “Enhanced with DFFS” button. When you have saved the configuration, the overlay should behave properly.

Hope this helps,
Alexander

[Alexander Bautz]

This will be added in the upcoming release.

Alexander

[Author]

Posts