Search Results for 'list form'

Home Forums Search Search Results for 'list form'

Viewing 15 results - 136 through 150 (of 1,358 total)
  • Author
    Search Results
  • #36696
    Johnathan Carter
    Participant

      Hi Alexander:

      Probably something simple but for some reason I’m stuck.

      List Fields
      – Requested By (People Picker)
      – Status (Choice)

      What I need:
      1. Set Status to “Pending Review“ when:
      – Requested By = {currentUser}
      – Status = “Action Required” on load

      2. Send Email to “Requested By” when:
      – Requested By <> {currentUser}
      – Status is changed to “Action Required”

      Current Rules:

      Set Status to “Pending Review“
      1. Requestor Is Current User
      – Trigger: Requested By = {currentUser}
      – Validate: Form Load
      2. Current Status Equals Action Required
      – Trigger: Status = “Action Required”
      – Validate: Form Load
      3. Update Status to Pending Review
      – Trigger: When this form is saved
      – Validate: Form load and field change
      – Linked Rules: Rule 1 and 2 above
      – Set field value: Status “Pending Review“

      Send Email to “Requested By”
      4. Requestor Is Not Current User
      – Trigger: Requested By <> {currentUser}
      – Validate: Form Load
      5. Status Changed to Action Required
      – Trigger: Status = “Action Required”
      – Validate: Field Change
      6. Email Requestor Action Required
      – Trigger: When this form is saved
      – Validate: Form load and field change
      – Linked Rules: Rule 5 and 6 above
      – Send or Stop Email: Email_Action_Req

      Rules 1, 2 and 3 gives the expected result. But I f I enable 4, 5 and 6. The Status changes to “Pending Review“ when I save the form even when rules 1 and 2 are false.

      Let me know if screenshots would help. I did try to debug. All the rules validate as intended… i believe… until I hit save.

      Help please!

      Thank
      John

      #36686
      Joe Penland
      Participant

        I am seeing an issue with the web part for showing forms on a site page. I love the functionality this web part is offering, but I have found a bit of an issue.

        When I open an item to view with that web part and click edit it seems the DispForm fields are just enabled so the fields can be edited. The actual EditForm is not loaded, so none of the rules or custom JavaScript from the EditForm work. They are never loaded because the actual EditForm is not loaded–the DispForm is simply converted to editable from read only.

        Steps to recreate:

        1. Add HTML section to DispForm with <h2>This is the display form.</h2>.

        2. Add HTML section to EditForm with <h2 style=”color: red;”>This is the edit form.</h2>.

        3. Open DispForm in Modern DFFS Formpage.

        4. Click “Edit.” The form does not switch as expected.

        I am attaching a screen recording of the issue. The first video shows the forms switching properly when loaded directly from the list. The second video shows how the forms do not switch when loaded in the web part on the site page.

        • This topic was modified 2 years, 1 month ago by Joe Penland.
        #36681
        William Summers
        Participant

          Greetings. Currently, using a multi-line text field with append comments, the one making the updated value saves the form and it places the person who created the list as the person who created the comment. In the attachment, it shows that Swapna was the one that created the comment even though William did. you can see the creator at the bottom. v1.0.17.0

          Attachments:
          #36670
          Marcus Khoo
          Participant

            I would like to report a strange effect and wondered if there was anything I could do about it.
            I notice that if i click a list item too quickly after a refresh of the list, the DFSS icon does not appear in the action bar and SharePoint complains that there is no DFSS form. If I wait a few seconds it is OK.

            Is there anything I can do about this?

            Thanks in advance
            /Marcus

            #36669
            Marcus Khoo
            Participant

              Hi,
              I found a strage bug.
              I have a form with 5 lookup fields on it.
              1. Lookup with values from list 1
              2. Lookup with values from list 2
              3. Lookup with values from list 3 but filtered by the “parent” value as selected in Lookup 2
              4. Lookup with values from list 2
              5. Lookup with values from List 3 but filtered by the “parent” value as selected in Lookup 4

              (List 3 contains a lookup to list 2 which is the “parent”)

              I also have a vLookup on this form and I have enabled the “New” button to create a new version of the same list item. I want to transfer Lookups 1, 2 and 4 into the new list item.
              This WORKS perfectly but here is the bug:

              In the new item Lookups 1, 2 and 4 are all populated correctly. However, for this new item the options in Lookup 3 are NOT correctly filtered. The options shown are repeating sets of the options I want.

              Stangely when I use Lookup 5 the options ARE filtered correctly by the selection in Lookup 4

              Summary: The behaviour is correct for the new Lookup 5 but incorrect for the new Lookup 3

              Hope that all makes sense to you Alexander.
              Best regards and congratulations on such an great product.

              #36655

              In reply to: Custom JS examples

              Joe Penland
              Participant

                There must have been something unusual going on, but I don’t know what. I tried reproducing it, but I couldn’t do it with a simple clean list. Not sure exactly what was happening, but I did get it resolved by overwriting the form with an export from a mirror list. Sorry about the false alarm and inability to reproduce the issue! Thanks for your help.

                #36653

                In reply to: Custom JS examples

                Joe Penland
                Participant

                  It turns out the issue was a rule/form configuration mismatch. The rule which was supposed to trigger on form load included hiding many fields, but the fields had been deleted from the form itself where the rule was being applied. This did not trigger any errors, and I never could get any output in the console even with debugging on, which seems strange still. However, I was able to rebuild the form and only hide fields which were actually present. With this configuration, the rule triggers and outputs to the console as expected.

                  So my conclusion is, it seems if the rule which triggers on form load is referencing fields that do not actually exist in the form (even though they exist in the list), the rule may break or otherwise not run–even though the trigger conditions are met (but I never got any error messages to prove this theory).

                  #36599

                  In reply to: Feature request

                  Alexander Bautz
                  Keymaster

                    You can do this with custom js – add this to your EditForm Custom JS:

                    function dffs_PostSaveAction() {
                      var url = location.pathname + "?DFFSForm=disp&DFFSID=" + getFieldValue("ID");
                      var list = getUrlKeyValue("DFFSList");
                      if (list !== null) {
                        url += "&DFFSList=" + list;
                      }
                      location.href = url;
                    }
                    

                    Alexander

                    Alexander Bautz
                    Keymaster

                      Thanks for the clarification – in case anyone wonders, this is the solution used to pull extra field values from a lookup field: https://spjsblog.com/2013/10/16/display-information-from-another-list-based-on-a-lookup-column-connection-updated-version/

                      Add this code to your custom js:

                      jQuery("#dffs_LookupColumnFIN select").on("change", function(){
                          setTimeout(function(){
                              var value = jQuery("#LookupColumnFIN_ExtraLookupFieldFIN").text();
                              setFieldValue("SetFieldFIN", value);
                          },1000);
                      });
                      

                      Replace LookupColumnFIN with the lookup field internal name, ExtraLookupFieldFIN with the extra field that you want to pull the value from and SetFieldFIN with the internal name of the field you want to write the value to.

                      There is a 1 second delay to allow for the data to be retrieved before grabbing the value.

                      Alexander

                      #36579
                      Jonathan Stamper
                      Participant

                        I’m getting close. I reuploaded DFFS back in to the SPJS folder which didn’t change the error. So then I took the bottom and top CEWPs from a working list on another site, exported them out and imported them into the troubled list. I updated the links on each pointed to the specified locations. It now brings up the updated DFFS edit version link at the bottom of the form but when I select it I’m presented with an error at the top of the page and can’t go any farther.

                        The site is a subsite and the SPJS folder is in that subsite. Should I put it on the main site and reference from there?

                        Attachments:
                        #36578
                        Joe Penland
                        Participant

                          Gotcha. Thanks for explaining.

                          I wanted to make sure you also saw the issue where the dffs_PostCancelAction() on a DispForm is getting triggered when you click the “Edit” button, not only the “Cancel” button. The dffs_PostCancelAction() executes before the form switches to the EditForm. I was seeing this behavior directly in the list when viewing an item and then clicking the “Edit” button.

                          Thanks again!

                          #36566
                          Joe Penland
                          Participant

                            A couple other things I noticed, which I thought I should mention:

                            It appears the redirect from the page with the web part executes BEFORE the dffs_PostSaveAction() and dffs_PostCancelAction() are executed. Because the redirect navigates away from the page, the post save or post cancel actions are never executed at all as far as I can tell.

                            Also, when the DispForm is open for an item (while in the list, not through the web part) it appears the dffs_PostCancelAction() is executed if you click the “Edit” button to edit the item. This causes problems if you are using the dffs_PostCancelAction() to redirect the user to a different page because the form was not actually cancelled.

                            Thanks again for all your work.

                            Jeff Lynch
                            Participant

                              I have a cascading dropdown that uses a value (case pack) to determine values in the dropdown. That value is actually stored in the item list, where the item (Product) is selected in a dropdown above. How can I get that value to use as the parent column in the form with the cascade?

                              List 1 – products fields include name and casepack
                              List 2 – casepack – value
                              List 3 – order item – includes lookup to product, and a field with partial case pack values, I want to use the casepack from list 1 to filter the dropdown in list 3 based on matches in list 2.

                              Joe Penland
                              Participant

                                Hi Alexander,

                                I noticed the web part you added which enables showing forms on a SharePoint page – thank you! This is really useful! I have been playing around with it and it seems to be working correctly overall – just like the forms work when in a list.

                                I did notice one slight difference, though, in regard to the DispForm. When viewing an item directly in the list, there are “Edit” and “Cancel” buttons available so a user can switch to the EditForm. However, when viewing an item’s form in a Site Page via the new web part, the “Edit” button is not present. Is this by design, or would it be possible to have the “Edit” button available like it is when viewing an item directly in a list?

                                Thank you!

                                #36554
                                Jonathan Stamper
                                Participant

                                  I created a UAT space and added the new DFFS items. When I try to install DFFS onto the forms of the UAT list I get an error message: Failed to add the DFFS WebPart(s) to “form name” The file you imported is not valid. Verify that the file is a Web Part description file (.webpart or .Dwp) that contains well-formed xml.

                                  Not sure how to proceed. I pointed the loader file to DFFS which is in SPJS doc library.

                                  I also don’t have any data in the UAT list yet.

                                Viewing 15 results - 136 through 150 (of 1,358 total)