Forum Discussion

RhondaJones's avatar
RhondaJones
Qrew Cadet
10 months ago

EOTI SAVE BUTTON

For the love of all things holy and before I throw my PC out the window....

I FINALLY got a button to add a new record to a child table with the prepopulated fields I need. Code is 

"<a href='" &
URLRoot() & "db/btcpg7sph?a=API_GenAddRecordForm&dfid=2" &
"&_fid_18=" & URLEncode([Related Request]) &
"&_fid_20=" & URLEncode([Request - Order Number]) &
"&_fid_19=" & URLEncode([Request - Name]) &
"'>" &
"<img src='https://expertclaimmanagement.quickbase.com/up/btegrvwjr/g/rb/eh/va/ADD%20NEXT%20ITEM.png' alt='Save & New'>" &
"</a>"

The problem is, of course, that it doesn't save the current form. So, I just set the application settings to auto-save if a page is navigated away from.  The problem is that it still throws the Leave site warning message which confuses the 75-year-olds using this form. 

So I created this button 

var text url = URLRoot() & "db/" & Dbid() & "?a=er&rid=" & ToText([Record ID#]);
var text link = "<a href='" & $url & "' data-replaceRid='true' style='font-size: 11pt;margin-left: 5px; margin-top: 0px; height: 33px; width: 160px; text-align:center;background-color:#13294d;color:white;background-image: linear-gradient(to bottom, #13294d 0%, #13294d 100%);' class='SaveBeforeNavigating Vibrant'>Save and Continue</a>";
$link

but it doesn't actually save and continue, it saves and next. It repopulates a blank form and if I test it as EOTI, I get an Access Denied page. 

I realize the EASIEST way to control this functionality is the built in save button. Unfortunately, the lamen user hits Save and close every.single.time. Even with huge bold instructions explaining how it works. Because they do not have access to their records once they close it, they have to start all over or, what actually happens, is call me and I spend all day on the phone. 

I either need a way to have a save button that returns the EOTI to the page in edit mode (and I guess be told how to make sure the permissions are set correctly) so that they can then hit the add next item button or close button, or figure out a way to allow EOTI to access records with either the Order Number they enter which is unique, or the record ID number without them being able to see everyone else's entries. 

I know this is very jumbled. I'm 10 hours in and ready to dissolve my business at this point. It feels like I am being forced to use the native buttons even when they are the worst solution. I miss Java Script. I hate it but I NEED three separate buttons. One to save and continue, one to close and one to Add New. I have the close and add new figured out. 



------------------------------
Rhonda Jones
------------------------------

8 Replies

  • Rhonda, Is the workflow that the user is adding a parent record and then needs to add a child record with a click that first saves the Parent and then passes the newly created Record ID# of the Parent into the Add Child button so as not to create an orphan child?



    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------
    • RhondaJones's avatar
      RhondaJones
      Qrew Cadet

      Mark,

      No. So, they enter some basic info in the parent record and then click a Add Items button which takes them to the first record to enter in the child table. this button is the one Quickbase creates when you make the parent/child relationship link.It works perfectly. It creates the first child record and displays the correct Record Id, Order Number and Name. In this situation, the Record ID is the reference proxy and the Order Number and Name are lookup fields. It is here that my older users are having an issue. It is creating the second child record that is the problem. They can't figure out the drop down save button that is the native UI. 



      ------------------------------
      Rhonda Jones
      ------------------------------
      • MarkShnier__You's avatar
        MarkShnier__You
        Icon for Qrew Legend rankQrew Legend

        Rhonda,

        I'm still confused about the workflow. They launch off a Parent record and land on add Add Child form.  So then is the issue that you want to provide a button on the Child record (still in Add Mode) which will auto save that unsaved child and land the user on a new Add Child form again?



        ------------------------------
        Mark Shnier (Your Quickbase Coach)
        mark.shnier@gmail.com
        ------------------------------
  • If you can control how they navigate to the form, I would use a code page that requires they enter their email address to proceed. 

    From there, the code page should create the new record, record their email address on the record, and navigate them to any form you want. 

    Finally, use QB to send them a notification with a link to the record. This way they always have a link to the record and shouldn't need to contact you if they get lost.



    ------------------------------
    gary
    ------------------------------