[Alexander Bautz]

I suggest you create a new rule that triggers on “No trigger (must be triggered manually)”. In this rule you add all the ReadOnly fields you want to set. Name the rule for example “DoAlotOfFieldsReadonly”

Now, in your Custom JS you call this rule like this to set all fields readonly:

spjs.dffs.triggerRule(["DoAlotOfFieldsReadonly"]);

Alexander

[Alexander Bautz]

I see,
the only way to install is to add it to either the tenant app catalog or the site collection app catalog. There is unfortunately no other option that I know of.

You can probably use PowerShell to install it, but I haven’t tested that myself so you must look at the PnP PowerShell documentation.

Alexander

[Alexander Bautz]

Thanks,
I have made one change that I’m pretty sure will prevent this issue in the future. I’ll publish a new version later this week.

Alexander

[Alexander Bautz]

Thanks, I’ll fix this in the next release.

Alexander

[Alexander Bautz]

Thanks for the clarification,
Unfortunately I was not able to recreate the error. What kind of field was “CreatorDepartment”? – maybe it is related to a specific field type.

Alexander

[Alexander Bautz]

Hi,
Where did you remove the deleted fields (what part of the config)? – I need to know to be able to catch this error in future versions.

Alexander

[Alexander Bautz]

I think this might be related to a field that has been deleted from the list, but it is used in for example a rule in the form.

I have made some changes earlier to try to catch this kind of errors, but I might have missed something.

Do you know if a field has been deleted recently? – if so, do you know where in the config it was used?

You can open the configuration list (/Lists/DFFSConfigurationList/AllItems.aspx) and manually edit the configuration blob to remove that field, or you can delete the config for that form to start over.

Alexander

[Alexander Bautz]

Is this a configuration you have made in an earlier version?

Do you see any errors in the developer console (F12 > Console) when you try to enter the configuration?

Alexander

[Alexander Bautz]

Try this instead:

.dffs-readonly-inner input[type=text]{
    width:100%;
    box-sizing: border-box;
}

Alexander

[Alexander Bautz]

Hi,
There is obviously some problems here – can you share the color theme settings so I can try to replicate it?

Alexander

[Alexander Bautz]

Hi,
Are you talking about the Classic DFFS? – the Modern DFFS is installed in the App catalog and you can add it to your tenant app catalog if you don’t want to add it to individual site collection app catalogs.

Alexander

[Alexander Bautz]

You can fix this by adding this snippet to your Custom CSS:

.spjs_chk_readonly_wrap input{
    width:100%;
}

Alexander

[Alexander Bautz]

You should use the installation method specified in the installation manual (v2): https://spjsblog.com/dffs/dffs-installation-manual/#InstallDFFS

Reinstalling will not affect the configs for your forms they will pop back when you have reinstalled DFFS.

Alexander

[Alexander Bautz]

OK, then I suggest that you update to the latest version (currently v4.4.5.51). It should fix this problem.

Alexander

[Alexander Bautz]

Hi,
Which version of the classic DFFS are you using? – I tested this in the latest version and it does work there.

Alexander

[Author]

Posts