Rule issue introduced in DFFS_v4.4.5.19 & .20

Forums Dynamic Forms for SharePoint Rule issue introduced in DFFS_v4.4.5.19 & .20

Viewing 6 reply threads
  • Author
    Posts
    • #33151
      BenR
      Participant

      Alexander,

      I hope you are well.

      I have an issue with one list configuration which seems to expose a difference in Rule processing between DFFS_v4.4.5.18 and DFFS_v4.4.5.19 – and carries on to DFFS_v4.4.5.20.

      ● The primary symptom is that when opening a form, NewForm, EditForm, or DispForm, will not complete rendering, resulting in the “This took forever!” error message. I have narrowed down this symptom to three linked rules.
      ● A secondary symptom is that disabling the three linked rules identified above does not remove the symptom, however deleting the three rules does.

      Notes:
      The unaltered configuration tested with the following versions:
      ● DFFS_v4.4.5.20 – FAIL
      ● DFFS_v4.4.5.19 – FAIL
      ● DFFS_v4.4.5.18 – SUCCESS
      ● DFFS_v4.4.5.17 – SUCCESS
      ● DFFS_v4.4.5.16 – SUCCESS
      In this configuration, NewForm was created first, and copied to EditForm and DispForm.

      The three rules (Nos. 2, 3, & 4) are linked:
      ● No. 3 to 2
      ● No. 4 to 2 and 3

      Each rule sets one Required field, and nothing else. Please see the attached images to illustrate the settings:
      ● Rule No. 2
      ● Rule No. 3
      ● Rule No. 4

      Please tell me what I can do to releave this error or to troubleshoot further.

      As always, your support and efforts are greatly appreciated!

      R’grds – Ben.
      Reference:

      Successful version:
      Version information
      Custom DFFS-folder: DFFS_v4.4.5.18_2021-03-05
      DFFS Loader: v2
      DFFS frontend: 4.4.5.18 – March 05, 2021
      DFFS frontend CSS: 4.64 /
      Autocomplete: 1.6.51 – February 07, 2021
      Cascading dropdowns: 3.7.44 – February 07, 2021
      jQuery: 1.12.4
      Lookup: 1.1.20 – March 10, 2020
      Resource management: 2.4.5 – August 29, 2019
      SPJS-Utility: 1.350 – February 21, 2021
      vLookup: 2.2.160 – February 21, 2021

      FAILING version:
      Version information
      Custom DFFS-folder: DFFS_v4.4.5.20_2021-03-21
      DFFS Loader: v2
      DFFS frontend: 4.4.5.20 – March 21, 2021
      DFFS frontend CSS: 4.64 /
      Autocomplete: 1.6.51 – February 07, 2021
      Cascading dropdowns: 3.7.46 – March 21, 2021
      jQuery: 1.12.4
      Lookup: 1.1.20 – March 10, 2020
      Resource management: 2.4.5 – August 29, 2019
      SPJS-Utility: 1.350 – February 21, 2021
      vLookup: 2.2.161 – March 21, 2021

    • #33158
      Alexander Bautz
      Keymaster

      Hi,
      I’ll have to look into this but was wondering if you had any error messages in the developer console (hit F12 > Console) when you try to load the form?

      Alexander

    • #33168
      BenR
      Participant

      Alexander,

      I’ve captured console errors only in the attached file, comparing DFFS_v4.4.5.18 (SUCCESSFUL) to DFFS_v4.4.5.20 (FAILING)

      R’grds – Ben.

    • #33171
      Alexander Bautz
      Keymaster

      Thanks,
      I’ll look at it and see if I can figure it out.

      Which version of SP are you running?

      PS: I deleted the attachment because you had a link in it.

      Alexander

    • #33173
      BenR
      Participant

      Alexander,

      My SP platform is SharePoint 2013 on premises.

      R’grds – Ben.

      • #33177
        Alexander Bautz
        Keymaster

        Thanks, I found the bug and will get a new version out before the weekend to fix it.

        Alexander

    • #33186
      Alexander Bautz
      Keymaster

      I have published a new version that should fix this issue. Please let me know how it works out.

      Alexander

    • #33195
      BenR
      Participant

      Alexander,

      Yes! Your fix has addressed my symptom, and I am now running v4.4.5.21 in production.

      As always, your support and efforts are greatly appreciated!

      R’grds – Ben.

Viewing 6 reply threads
  • You must be logged in to reply to this topic.