Jonathan Stamper

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 85 total)
  • Author
    Posts
  • in reply to: Variables & Callbacks on vLookup Views #34678
    Jonathan Stamper
    Participant

    That’s a good point. I ended up hosing it for now.

    One-off question – does spjs.dffs.alert have a timeout feature? I was going to do an alert popup that would show up for about 3 seconds and then disappear.

    in reply to: Callback for removing multi-selection AC #34469
    Jonathan Stamper
    Participant

    That was it! Just needed some time before executing. I even included a 3rd option to catch the mouse up event on the spjs_acItem class to continue appending the field next to it as the user starts clicking items all in one go.

    Though it’s a rough/ugly way of setting other fields using multi-select ac it works great!

    in reply to: Callback for removing multi-selection AC #34452
    Jonathan Stamper
    Participant

    Ah dang the mouse up is close but still returns the removed item using SetFieldValue. I tried “change” and that didn’t work either. I tried to create a rule but since my ac field is actually a multi-line plain text field I don’t think I can create a rule on that.

    in reply to: Callback for removing multi-selection AC #34405
    Jonathan Stamper
    Participant

    I like that! I appreciate it?

    in reply to: Autocomplete only works on new child form #34274
    Jonathan Stamper
    Participant

    I figured it out…

    • I had some old AC code in my Custom JS section of the child forms. I’m using external js files now, with the ac inside a function, so it was conflicting
    • Once I removed the old Custom JS, the AC on the New child form worked correctly calling the ac function in vLookupPresetFromURLDone
    • Finally, the edit form stopped working with AC until I called it in dffs_ready within an if statement using spjs.dffs.data.isEditForm

    Glad I got that working as that was causing some headaches haha.

    in reply to: Autocomplete only works on new child form #34273
    Jonathan Stamper
    Participant

    Oh, I think I see why, it’s based on when the child form loads. I’m using vLookupPresetFromURLDone(fin) but it’s almost like it needs to literally wait until everything has loaded to capture. I have it on dff_ready and that doesn’t seem to work either.

    I’m not sure if there is another onLoad option.

    in reply to: Autocomplete only works on new child form #34272
    Jonathan Stamper
    Participant

    My apologies, in the title it should have said “Only works on Edit form”

    in reply to: Set Value of Auto Complete #34242
    Jonathan Stamper
    Participant

    Ok, I’ll try that out. In terms of when/where the action would occur it would be after returning to the main form from child form and/or during dffs_ready and pre-save.

    in reply to: Set Value of Auto Complete #34225
    Jonathan Stamper
    Participant

    I’m doing light “data integrity” between what the requestor chooses in the main AC, and what is/isn’t available as a list item in a vLookup/child list. Only Admins can add to the vLookup/child list and I wanted to attempt to auto-update the AC values on the main form to reduce manual updating.

    Right now, I have it set up where if a requestor adds items in the main AC field, when they save the request, the selections are then created as list items in the child list for additional usage and future reporting opportunities.

    in reply to: Set Value of Auto Complete #34221
    Jonathan Stamper
    Participant

    Does setFieldValue work for a multi-select AC? I’m trying to use the logic from the manual below but I may have it in the correct format for a multi-select.

    spjs.ac.setFieldValue("AutocompleteFieldInternalName","The_Selected_Value");
    Jonathan Stamper
    Participant

    Oh cool! That should work better! Thank you so much for all the help.

    Jonathan Stamper
    Participant

    Ah-ha! I just wrapped the ac in

    
    
    window.addEventListener(‘load’, function(){
     spjs.ac.textfield({…});
    });

    That seems to have worked, unless there is a better approach.

    Jonathan Stamper
    Participant

    I got it working. I ended up just using the .css(“visibility”,”visible/hidden”) action with conditionals for the button and table.

    I couldn’t get options mentioned for spjshidden to work without it reappearing when I clicked to another tab or showing once I clicked to another tab and then returned.

    Jonathan Stamper
    Participant

    For some reason, when ran in dffs_ready, the button or table won’t show/hide initially until I go to another tab then return to the attachments. No issues in the code nor on the console. I do have the setting turned on to remember where you left off on the form. Could that be causing he issue or maybe Should put them in an onload/ready function?

    Actually as an update, I turned off the “remember” functionality but that causes me to have to click the attachments tab, click another tab then back to attachments to see the button or table.

    Jonathan Stamper
    Participant

    I think I got it. I created a button that initiates the attachment setup, creating the folders and sub folders. The only thing left is preventing the vLookup from initiating until after the attachment setup click, or would it be better to have the vLookup wrapper hidden instead and then just JQuery to show and refresh?

Viewing 15 posts - 46 through 60 (of 85 total)