Sebastian Ganson

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • February 21, 2017 at 22:05 in reply to: Custom JS or Rules to show/hide multiple fields #15780
    Sebastian Ganson
    Participant

      One more quick thing I forgot to mention before – you may want to update the documentation to specify using the SharePoint Internal Field Name in the JavaScript code step when identifying the value for dffs_formTypeSwitch to handle non-pretty version field names 🙂

      February 21, 2017 at 16:04 in reply to: Custom JS or Rules to show/hide multiple fields #15762
      Sebastian Ganson
      Participant

        That’s great! If I can make one small enhancement suggestion / request, would it be easy to add a “default” function to the overall versioning routine? In other words, right now if a user opens a list item where the “versioning” field is a value which is not found in the list of available ?formType= values, it defaults to opening the view/edit form as though no DFFS backend has been configured (e.g. showing all fields, etc.). It would be helpful to be able to create and set a default form (for example the blank “?formType=” versions of the Add/Edit/View) from which we could prompt them that they have an unsupported version item and prevent them from taking further action.

        February 15, 2017 at 16:06 in reply to: Custom JS or Rules to show/hide multiple fields #15650
        Sebastian Ganson
        Participant

          Thanks, Alexander! It looks like this is exactly what we’re looking for.

          One quick thing I noticed and wanted to bring to your attention is that in a certain circumstance DFFS does not properly create a “versioned” entry in the SPJS-DynamicFormsForSharePoint list. I believe you can recreate the scenario as follows

          – go in to the DFFS Backend of a “versioned” form, e.g. Edit, and select to Switch to NewForm or DispForm
          – if the Form configuration you select to switch to does not already exist, DFFS will prompt you to either create new or select from an existing list config
          – selecting a “versioned” config to copy from (e.g. lists/listname/dispform.aspx?formType=3) creates a copy called (if switching to Edit) lists/listname/editform.aspx – ie. the version ?formType=3 is not included.

          This may be by design, but it seems to me you’d want to (optionally?) include the version.

          In either case, correcting the missing version details was as easy as editing the Title in the item in the SPJS-DynamicFormsForSharePoint list and appending the appropriate version information.

          Thanks again!
          Sebastian

        • Author
          Posts
        Viewing 3 posts - 1 through 3 (of 3 total)