[Alexander Bautz]

I’ll investigate and get back to you.

Alexander

[Alexander Bautz]

I have confirmed the bug and will fix it in the next release.

Alexander

[Alexander Bautz]

You can find an example here: https://spjsblog.com/forums/topic/custom-js-examples/#post-38138

Alexander

[Alexander Bautz]

Hi,
A similar bug was fixed in v1.0.81 in January 2025 – which version of DFFS are you running in this form?

Alexander

[Alexander Bautz]

Hi,
I don’t have any solution to this ready, but from what you explain it could be done using custom js and HTML to build a checkbox list and then store the data in a multiline plain text field as a JSON object.

I don’t have any code examples, but basically what you would want is an array of the subtasks and a completed property – something like this:

[
    { id: 1, label: "Task #1", "completed": false },
    { id: 2, label: "Task #2", "completed": true },
    { id: 3, label: "Task #3", "completed": false },
    { id: 4, label: "Task #4", "completed": false }
]

Then you would use JavaScript in Custom JS to read the array and draw a HTML list of checkboxes / labels. When checking the box it writes back to the JSON data object and storing the data in a multiline textfield.

Alexander

[Alexander Bautz]

Hi,
I’ll get the help text fixed in the next version. You must change the value to true / false for it to work on a boolean field – like this:

[
    {
        "operator": "=",
        "value": false,
        "style": {
            "backgroundColor": "red"
        }
    },
    {
        "operator": "=",
        "value": true,
        "style": {
            "backgroundColor": "yellow"
        }
    }
]

PS: I found that if you have a whitespace as the first character in the conditional formatting, it won’t work – this will be fixed in the next version.

Alexander

[Alexander Bautz]

I have found and fixed the issue with the missing “Get information from” in the top of the field properties panel, but I’m not able to recreate the error you are experiencing.

Can you take a few screenshots and email them to me so I can try to replicate exactly the same setup as in your case (same field type and same viewfield selected in the “In this column” in list settings for that field).

Alexander

[Alexander Bautz]

It looks like there is something off with this field – look at my attached field and compare with your (your screenshot if missing the list and field info).

Try creating a new lookup field to the same list and see if that works.

I have a hunch about what it could be: Did you maybe create the lookup field from the list view (by clicking Add column button?) and not by going to the list settings to add the field? – I think I saw something similar a while back where the field was missing some parameters or they were in a different format when creating the field from the list view.

Alexander

Attachments:

1. 

   Lookup_Field_Props.png
   

[Alexander Bautz]

It looks like the screenshot is from Editform and not Displayform, but I’m not able to recreate the error.

Is this lookup field a standard lookup field created in list settings, or a specific “related items” lookup field from a site column?

Have you applied any filters on the lookup field in the DFFS configuration? – can you show me a screenshot of the “Field properties” panel?

Alexander

[Alexander Bautz]

Hi,
I found that the email you had on your user was the old domain for your company – I have changed it to the new so you should receive email notifications again.

Alexander

[Alexander Bautz]

Yes, but only in DispForm as in an out-of-the-box SharePoint list.

Alexander

[Alexander Bautz]

Hi,
Not sure why you wasn’t alerted – the email sending seems to be OK.

I’ll include the two first options as s first release – probably within a few weeks from now so you can test it.

I figured the third option would be a bit more complicated to get implemented so I’ll wait until there is demand for it.

Best regards,
Alexander

[Alexander Bautz]

Hi,
This does look like something cooked up by AI… Keep in mind that AI will aim to please you, but sometimes just imagines things.

Try changing the function like this (I have not addressed the rest of the code – it might work, but I haven’t tested it):

function checkAndDisableField() {
    var val1 = getFieldValue("Control_x0020_Certified_x003f_");
    var val2 = getFieldValue("Checklist_x0020_Certified_x003f_");
    var val3 = getFieldValue("Checker_x0020_Inventory_x0020_Ce");
    var allYes = val1 === "Yes" && val2 === "Yes" && val3 === "Yes";
    if(allYes){
        spjs.dffs.doReadOnly(["Requesting_x0020_an_x0020_Except"]);
    }else{
        spjs.dffs.undoReadOnly(["Requesting_x0020_an_x0020_Except"]);
    }
}

PS: Wrap any code you want to post inside <pre>…code here…</pre>

Alexander

[Alexander Bautz]

It looks like your code snippet is cut off at the bottom. Can you show me the complete “checkAndDisableField” function?

Alexander

[Alexander Bautz]

Sorry, but I don’t have any solution for adding multiple attachment fields in the classic DFFS (it is possible to do that in the Modern DFFS version in SharePoint online).

An alternative for you would be to use the vLookup plugin and to store the attachments in a document library – tagged with metadata to associate them with the current list item. See the example for general vLookup configuration here: https://spjsblog.com/vlookup-for-sharepoint/vlookup-setup-example-for-sp-2010-and-2013/

Alexander

[Author]

Posts