BenR

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 53 total)
  • Author
    Posts
  • in reply to: Timing issue: Autocomplete vs. Cascade #37652
    BenR
    Participant

    Alexander,

    Your simple rule – AC, then CASC – worked! I moved the CASC into Custom JS below AC and found it working as I need.

    As always, your support and efforts are SO appreciated!

    R’grds – Ben.

    in reply to: Timing issue: Autocomplete vs. Cascade #37650
    BenR
    Participant

    Alexander,

    Additional clarification… The first tier of the Cascading dropdown successfully populates. The second tier and on down to fifth tier do not populate (this is where the timing function spjs_casc_ready() should come into play).

    There are no errors reported in Console, tested in Edge (IE mode) and Google Chrome.

    R’grds – Ben.

    in reply to: Timing issue: Autocomplete vs. Cascade #37648
    BenR
    Participant

    Alexander,

    Returning to this issue 5-years later…

    I have a 5-tier Cascading Dropdown set on the Cascading dropdowns menu in DFFS – this is working perfectly (SCLOB1, SCLOB2, SCLOB3, SCLOB4, SCLOB5).

    Added to this, I am using Autocomplete which will write to these Cascading Dropdown fields. In the past, the timing issue of Cascading vs. Autocomplete was circumvented with this guidance: https://spjsblog.com/dffs/dffs-plugins/spjs-cascading-dropdowns/#Callback_function_when_select_is_filled. However, it seems not to be working… To support Autocomplete, I move values into LOB2Temp, LOB3Temp, LOB4Temap, and LOB5Temp. Then, use function spjs_casc_ready() to move those values into the Cascading Dropdown fields.

    This has worked well in the past… I have attached the code for Autocomplete and function spjs_casc_ready() – do you see anything wrong?

    As always, your support and efforts are greatly appreciated!

    R’grds – Ben.
    Reference:
    Version information

    Custom DFFS-folder: DFFS_v4.4.5.50_2024-04-05
    DFFS Loader: v2
    DFFS frontend: 4.4.5.40 – April 04, 2024
    DFFS frontend CSS: 4.65 / 4.65
    Autocomplete: 1.6.56 – April 04, 2024
    Cascading dropdowns: 3.7.48 – September 22, 2021
    jQuery: 3.6.3
    Lookup: 1.1.20 – March 10, 2020
    Resource management: 2.4.5 – August 29, 2019
    SPJS-Utility: 1.356 – November 20, 2021
    vLookup: 2.2.166 – April 04, 2024

    Licensed to

    …..

    BenR
    Participant

    Alexander,

    Thank you! I can confirm that errors regarding vLookup and Autocomplete are both resolved. In Edge browser (in EMIE mode), vLookup resolves, allows adding a new child record, and in DFFS configuration, there is no error for Autocomplete.

    Thank you SO much for supporting Classic DFFS! You certainly keep your audience happy!

    Sincere regards, Ben.

    BenR
    Participant

    Alexander,

    I wanted to report back to you on an earlier issue – vLookup not working in Microsoft Edge Browser… I’ve heard back from my support organization and offer additional info

    – Microsoft Edge Version 121.0.2277.112 (Official build) (64-bit).
    – Our on-prem SharePoint Server 2019 – this SharePoint is in Edge-IE Mode (Enterprise Mode for Internet Explorer (or EMIE) a compatibility mode where Internet Explorer is required). This allows Edge to emulate IE11.

    In Edge, when opening NewForm or EditForm (where vLookup is required), two errors reported in Developer Tool Console:
    – SCRIPT1002: Syntax error, SPJS-ac.js (10,1)
    – SCRIPT1002: Syntax error, SPJS-vLookup_frontend.js (9,1)

    From NewForm or EditForm, open DFFS configuration, one error reported:
    – SCRIPT1002: Syntax error, SPJS-ac.js (10,1)

    From DFFS configuration page, select [Autocomplete] button, displays:
    – The SPJS-Autocomplete plugin is not loaded.

    Does this information identify how to troubleshoot where vLookup in Edge is needed?

    Thank you so much for your support and efforts!

    R’grds – Ben.

    BenR
    Participant

    Alexander,

    Right you are! All working now in Google Chrome! When I hear back from my support organization about my Edge version, I’ll let you know what I find out.

    In the meantime, thank you so much for your support, patience, and efforts for Classic DFFS!

    R’grds – Ben.

    BenR
    Participant

    Alexander,

    I have opened a ticket with my support organization and will let you know what I find out.

    In Chrome, when I add a new item to the Parent list, I see the vLookupID field populated (works!). From the NewForm in the Parent list, I click to add a new item (to child), a dialog box opens and displays the whirly-gig and eventually resolves to β€œThis took forever!” Developer Console reports the error in the attached file.

    What can we do to troubleshoot?

    BenR
    Participant

    Alexander,

    Found an issue – vLookup is sensitive to the browser! My firm provides three browsers, Chrome, FireFox, and Edge. Recently, I’ve switched to Edge because of two features in SharePoint that it does, but Chrome and FireFox do not (Data View Properties – XSL or Parameters Editors, and multi-line paste to Data Sheet View).

    Browsers:
    Edge – Version 121.0.2277.112 – vLookup not loading
    Chrome – Version 120.0.6099.217 – vLookup working
    FireFox – Version 115.3.1esr – vLookup working

    Switching to Chrome (I will advise users on the landing page to use Chrome to work on this site…).

    Now that things are displaying on all forms correctly, I have a remaining problem…

    When I add a new item to the Parent list, I see the vLookupID field populated (works!). From the NewForm in the Parent list, I click to add a new item (to child), a dialog box opens and displays the whirly-gig and eventually resolves to “This took forever!”

    If I manually create the child record, copying the parent vLookupID, it will display correctly in the parent. So, the problem is with creating a new child record (from either parent NewForm or EditForm – I have created the _vlookupID and _vlookupParentID).

    Do you have advise how to troubleshoot this create child record issue?

    I am overwhelmed that you are helping me with Classic DFFS!

    R’grds – Ben.

    BenR
    Participant

    Alexander,

    Yes, the Content Editor Web Part on the installer page is pointing the new SPJS installation I built from scratch – see attached.

    Note that other DFFS functions are fine, just vLookup failing.

    Really appreciate your insight!

    R’grds – Ben.

    BenR
    Participant

    Alexander,

    Following your instructions, I have rebuilt from scratch.
    1) New download of latest Classic DFFS, new Installer_v2
    2) Create new SP Subsite, create new Lists – see DFFS vLookup 1.png
    3) Installer_v2 to new Parent list – see DFFS vLookup 2.png – note that the Attachments icon is displayed simply by adding DFFS to the NewForm.
    3) Turn off attachments for the list – see DFFS vLookup 3.png – note that the Attachments icon displays below the fields, but not on the Ribbon.
    4) Configure DFFS for NewForm, configure vLookup for NewForm- see DFFS vLookup 2.png – note that the Attachments no longer displayed,
    Title of vLookupVersions field not displayed,
    Magnifier Glass not displayed,
    Add new child (+) not displayed,
    The version information still says that vLookup is no loaded.

    Does this help troubleshooting?

    R’grds – Ben.

    BenR
    Participant

    Alexander,

    Thank you for your response. It has been quite a while since I last used the Classic DFFS vLookup configuration – I may be rusty, but have used it before.

    My issue is that in a NewForm or EditForm, the vLookup appears to be working partually… In the NewForm, the title of vLookup field (vLookupVersion) is inhibited (as set in vLookup configuration) – however the magnifying glass and add-new-child icons are not displayed. Additionally, an Attachement icon (paperclip) is displayed. Please see attached screenshot.

    I’ve confirmed that the Attachment icon is added by DFFS by removing it from NewForm, icon disappeared, add DFFS back onto NewForm – icon appears.

    As always, I appreciate your support and efforts!

    R’grds – Ben.

    in reply to: Cascading Menus – force one item to bottom of list… #35042
    BenR
    Participant

    Alexander,

    YES! Success!

    Thank you for your patience – I know you support many users, but you stayed with me and guided me to success.

    Stay well, R’grds – Ben.

    in reply to: Cascading Menus – force one item to bottom of list… #35038
    BenR
    Participant

    Alexander,

    Very good – now the sort is modified, but “Other” is moved to the top of the list instead of at the bottom.

    Is there another tweak you can recommend?

    R’grds – Ben.

    in reply to: Cascading Menus – force one item to bottom of list… #35034
    BenR
    Participant

    Alexander,

    I’m only part way successful. I have removed the this particular Cascade from the Cascading Dropdown tab, and manually invoked from the Custom JS tab. (Should I mention that I have two other Cascades specified in the Cascading Dropdown tab?).

    The cascade works, however the sort seems not to have an affect – the list still follows standard alphabetic sort.

    This is what I have assembled… The letter I would like to force to the bottom of the list is “O”, and tier-1’s internal name is “Title”

    
    
    //Manual invocation of Cascade for ProductLineL1
    spjs.casc.customSort.Title = function(a, b) {
        // Put O last in the dropdown
        if(a.text === "O" || b.text === "O"){
            return -1;
        }
        // Normal alphabetic sorting
        if(a.text < b.text){
            return -1;
        }
        if(a.text > b.text){
            return 1;
        }
        return 0;
    };
    
    spjs.casc.init(
     {
     "manualMode":true,
     "dataSource":"",
     "lookupList":"ProductLines",
     "lookupListBaseUrl":"https://sp.REDACTED.net/sites/spptdgsl/VPP",
     "lookupListFields":["Title","ProductLineL2","ProductLineGrouping"],
     "thisListFields":["ProductLineL1","ProductLineL2","ProductLineGrouping"],
     "setFields":[],
     "dropDownDefaultvalue":"- Select - ",
     "filter":"",
     "hideEmptyDropdowns":false,
     "autoselectSingleOption":true,
     "clearInvalidSelection":false,
     "addOwnValue":false,
     "addOwnValueMouseover":"",
     "cancelOwnValueMouseover":"",
     "sideBySide":true,
     "multichoiceDelimiter": ";" + String.fromCharCode(13, 10), // this represents a semicolon and a linefeed
     "debug":false
     }
    );

    Does this look right?

    As always, your support and efforts are appreciated!

    R’grds – Ben.

    in reply to: Rule issue introduced in DFFS_v4.4.5.19 & .20 #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 15 posts - 1 through 15 (of 53 total)