[Amal Vellappillil]

Any update on this?

[Amal Vellappillil]

Email with attachments have been sent.

[Amal Vellappillil]

I am having similar (but may be different) issue. I am using v1.0.66.0.
I had exported configuration for a list from our on-premise SharePoint to SharePoint online list. I imported settings for view and edit, both imported fine and the form loads when clicked I try to view or edit a record. However, I am unable to go back into the configuration for these forms anymore. I see there are some errors in the dev console. I have attached a screenshot here.

So instead of importing the configuration for “New” form, I just created one default one. The form loads and I am able to go back and edit the configuration for “New” form as well.

It feels like the import may have brought in some old code that is messing with the way Modern DFFS works. The exported configuration had custom js and custom css in it.

Is there a way to remove configuration from a particular list form? I was unable to find that information as well.

Attachments:

1. 

   modern-dffs-form-configuration-not-loading-error.jpg
   

[Amal Vellappillil]

Around 50 configs spanning across 8 subsites in 1 site collection.

[Amal Vellappillil]

I have the “Return to DispForm when editing an item and NOT opening the form in a dialog” checked under “Misc” tab. Is there a way to bulk update all list configurations in a site to have this option unchecked?

[Amal Vellappillil]

Thank you Alex. The suggested solution makes it much easier than adding the code snippet to each and every form.

[Amal Vellappillil]

Hey thank you for the quick work around. This does work with some change in user usage.
Is there a way to make this as a default on a site collection or site level? This would be great rather than going to each and every list and all its different forms and adding the snippet.

Or is there a way to load another javascript file whenever DFFS loads? I know there is the “Load these files before executing the Custom JS” feature per list per form level. Wondering if there is a possibility to add something similar on a site or site collection level.

• This reply was modified 3 years, 8 months ago by Amal Vellappillil.

[Amal Vellappillil]

Hi Alex,

Thank you for your reply. I did try to use the setFields functionality of autocomplete configuration. However, it seemed like setFields is not allowed for autocomplete field that accepts multiple values. It does give an error saying not available. Are you aware of this?

Thank you,
Amal Vellappillil

[Amal Vellappillil]

Hi Alex,

Thank you for explaining how things work in SPO.

I have attached the following screenshots.
1. Modified workflow
2. Create Stop variable as Integer
3. CurrentItem Stop as Integer (looking up)

Attachments:

1. 

   Screenshot-workflow-setup-1.jpg
   

2. 

   Screenshot-create-stop-variable-as-int.jpg
   

3. 

   Screenshot-currentitem-stop-as-int.jpg
   

[Amal Vellappillil]

Yes, it seems as if the boolean variable is not getting set with Yes/No values. Rather its getting set with True/False.

In any case I tried creating a an integer variable and setting value from Stop field. I then used that variable and checked if it equals 1. If 1, then stop the workflow. This seem to have worked. You can may be update your documentation to use an Integer variable rather than using a Boolean variable and check for 1. This might be helpful for those who are still in On-Prem SharePoint.

Out of curiosity, what do you use to send future dated emails in SharePoint online?

[Amal Vellappillil]

Hi Alex,

Yes that would work also. However, as you can imagine if we have 20 rules or so, that means we will need another 20 rules to make it work. Its better to use customJS at that point to check if the value changed based on the ruleID and triggerField.

Do you think this can be a feature added to a future release? A new operator or a checkbox next to the operator dropdown asking “is changed from initial value”? I think it will help.

Thank you for taking the time to provide a solution.

-Amal Vellappillil

• This reply was modified 4 years, 2 months ago by Amal Vellappillil.

[Amal Vellappillil]

Glad you are able to look into this and possibly skip duplicate calls to presaveaction method. It would be nice if the library could handle the logic than users remembering the little quirk and do the workaround on each and every form.

[Amal Vellappillil]

Sounds good to me 🙂

[Amal Vellappillil]

Hi Alex,

I have a suggestion/enhancement request. I noticed that it would be very helpful to have all the field names available as intellisense in Ace editor. So I added this to your “aceAutocomplete” function inside DFFS_backend js file.

var fieldNamesCompleter = {
                    getCompletions: function(editor, session, pos, prefix, callback) {
                        var wordList = spjs.dffs.data.listFieldsArr.map((f) => f.fin + "|" + f.disp + "|" + f.type); 
                        callback(null, wordList.map((word) => {
                            var wordArr = word.split("|");
                            return {
                                caption: wordArr[1] + " - " + wordArr[2],
                                value: wordArr[0],
                                meta: "listField"
                            };
                        }));
                
                    }
                }
                a.completers.push(fieldNamesCompleter);

This code was added inside the else block where you are setting enableBasicAutocompletion: true. You can use this as is or modify to your willing to adapt to your coding styles. I hope this gets added to the future versions of DFFS.

Thank you,
Amal Vellappillil

[Amal Vellappillil]

So I put debugger at the top of the presaveaction function and sure enough it got hit twice. So I still dont understand what is causing it to be called twice, but the workaround you mentioned skips the item creation the second time around.

Thank you so much for the workaround and tips on debugging.

[Author]

Posts