[Alexander Bautz]

NewForm and EditForm configurations are often different to let the first person use a simple form and then have a more complex form with more fields in editform.

I think the best solution would be to add an option to turn off quick save (I’ll look at adding that to the next version) so you can use the dffs_PostSaveAction custom js function to redirect to the EditForm configuration.

Alexander

[Alexander Bautz]

Hi,
If you look at this thread and find the Do something before the item is saved section you can just use getFieldValue(“Your_field_name”) to get the value to build your new variable with the changes, and setFieldValue(“Your_field_name”, your_variable); to write it back to the field.

Alexander

[Alexander Bautz]

I haven’t seen this error myself. It refers to the built in object _spPageContextInfo and it tries to read the pageListId from that object.

If you are able to recreate the issue it would help me to troubleshoot if you could bring up the developer tools and type this in the console and send me the output (expand the object) by clicking the triangle to the left of the output:

_spPageContextInfo

Alexander

[Alexander Bautz]

No worries, the Modern DFFS is a SharePoint framework app.

Alexander

[Alexander Bautz]

The configuration for Modern DFFS is stored in a list in each site. The list is hidden, but you can access it on this URL:

/sites/your_site/lists/DFFSConfigurationList

If you include this list (with contents) in your package, DFFS will load the config as soon as the Modern DFFS App is installed in the App Catalog.

Alexander

[Alexander Bautz]

Hi,
I have confirmed the bug and started work on it during the weekend, but was not able to finish it. I hope to get a new version out later this week.

Alexander

[Alexander Bautz]

Thanks for the clarification. I have started work on it during the weekend, but found some other issues I need to figure out. I hope to get a new version out later this week.

Alexander

[Alexander Bautz]

This error is the one fixed in v45 – it was introduced in v37.

Alexander

[Alexander Bautz]

Add something like this to your custom js:

var arrOfFields = ["Q1_x0020_Status", "Q2_x0020_Status"];

arrOfFields.forEach(fin => {
    jQuery("#dffs_" + fin + " select").on("change", function(){
        triggerChangeChoiceFields();
    });
});

function triggerChangeChoiceFields(){
    var hasFail = false;
    arrOfFields.forEach(fin => {
        if(getFieldValue(fin) === "Fail"){
            hasFail = true;
        }
    });
    if(hasFail){
        // Do your custom action here - for example call a rule that is set up with "Not trigger (must be triggered manually)"
        spjs.dffs.triggerRule(["customTrigger"]);
    }
}

This code triggers a rule called customTrigger – set up with the trigger “No trigger (must be triggered manually)”.

Let me know how this works out.

Alexander

• This reply was modified 1 year, 2 months ago by Alexander Bautz. Reason: Fixed code snippet format

[Alexander Bautz]

If you use code to hide fields in a row with side-by-side fields there is unfortunately no built in functionality to hide the “outer” row when all fields in the row have been hidden by rules.

The only way to do this is to use custom js – for example on an interval – to check if all fields have been hidden and then hide the outer row.

Alexander

[Alexander Bautz]

Hi,
I need some clarifications: are you trying to copy from a multilookup field in the parent to a multilookup field in the child and only the first item is transferred, or are you trying to transfer values from multiple different lookup fields and only the value in the first field is transferred?

Alexander

[Alexander Bautz]

In DFFS this setting is found in the Misc tab > Multi lookup columns > Arrange multi lookup columns vertically.

Alexander

[Alexander Bautz]

Hi,
I tested it and it seems to works as expected. Please note that the modern DFFS solution is a list view command set extension and only loads when the command bar is visible (edit > Show command bar).

Alexander

[Alexander Bautz]

I think there is a built in check in the browser that prevents the function to run in the form has not been modified – try changing at least one field and see if the code runs when you try to exit.

Alexander

[Alexander Bautz]

The code to tap into the PreSaveItem function worked in my test, but you must ensure you run the originalPreSaveItem and not use “return” in the code above the call to this function.

Alexander

[Author]

Posts