[Alexander Bautz]

This is now fixed in a new version. Only the SPJS-AC.js file is changed so you can just replace that one, but to ensure the browser cache is cleared you should open the DFFS installer and click the “Update loader file” button.

Alexander

[Alexander Bautz]

It is a bug that was introduced in the latest version to fix an issue where when clearing a single choice AC the hidden input field was not cleared. I forgot to account for multichoice on this field and this causes the hidden textarea to be cleared when clearing the ac-search field.

I’ll get it fixed in a new version later today.

Alexander

[Alexander Bautz]

I think this is better solved using some custom js. If you can show me how the fields are set up with the options I can give you an example of a script you can use.

What you basically want to have is an array of all the internal names, loop over them and add an eventlistner to the click of the field and in this click function loop over the fields again to check all values – if any of them are true, trigger a rule that does what you need it to do.

Alexander

[Alexander Bautz]

It is hard to tell without looking at the code live, but looking at it you might want to join the array with semicolon when writing it to the field – like this:

jQuery("#customMultichoiceSelector").find("input:checkbox:checked").each(function (i, elm) {
    arr.push(jQuery(elm).val());
});
setFieldValue(fin, arr.join(";"));

Alexander

[Alexander Bautz]

I don’t think there is any other way than to reduce the number of fields. You can split a large list into multiple lists connected using vLookup (plugin to DFFS).

Alexander

[Alexander Bautz]

Hi,
If you use the editProps method described here you get an edit item link: https://learn.microsoft.com/en-us/sharepoint/dev/declarative-customization/formatting-syntax-reference#customrowaction

The modern DFFS will work with the editProps and defaultClick options.

Alexander

[Alexander Bautz]

This is a know issue that I have raised a request with Microsoft about. It affects all solutions of this type – not only DFFS when you update / install a new version.

From my testing it only affects Google Chrome.

It can be fixed by waiting 10-15 minutes, or by clearing the browser data as described here: https://spjsblog.com/forums/topic/starting-to-see-this-error-message-on-any-dffs-enabled-site/#post-37263

Alexander

[Alexander Bautz]

I have published v1.0.40.0 that should fix the problem – let me know how it works out.

Alexander

[Alexander Bautz]

I have confirmed the bug and looking at it it looks like this never actually worked. I had mistakenly used both defaultSelectedKey and selectedKey on the dropdown so it would always show “And” even even if you changed the value to “Or”. If you did change it to “Or” it would actually save “Or” even if the dropdown shows “And”.

I’ll get this fixed in a new version later this week.

Alexander

[Alexander Bautz]

I’ll look into it.

Alexander

[Alexander Bautz]

Sure, I can move it to the left in the next version.

Alexander

[Alexander Bautz]

Not sure if vLookup would be the correct approach here if you want to auto-add the item on save as vLookups are designed for manual additions.

You could of course add the items in code before saving the items and then use vLookup to show the items (without showing the add-new-button) to avoid having to write the “show items code”, but do the addition in code in custom js.

Alexander

[Alexander Bautz]

When you enter the DFFS configuration either from the DFFS Installer “Direct to backend” or by clicking the “Enhanced with DFFS” from NewForm you don’t have an ID to a list item in the URL. If you then switch to edit the configuration on DispForm or EditForm and then save and exit, you are returned to the list and the form you are currently editing. If this is DispForm or EditForm you will see this message because the form expects the ID attribute to be in the URL to load the item with that ID.

Just click cancel to get back to the list and click an item to view or edit and all should be OK.

Alexander

[Alexander Bautz]

Thanks, I have confirmed the bug and will fix that and a few more over the weekend.

The bugs are a result of a rebuild of the save function to use another REST Endpoint. This endpoint expects a different format on the data that is committed and I missed a few field types in my testing obviously (like boolean fields and now people pickers).

Sorry for the inconvenience,
Alexander

[Alexander Bautz]

Which version are you using?

Alexander

[Author]

Posts