Forum Discussion

MackenziePhilli's avatar
MackenziePhilli
Qrew Trainee
5 years ago

Native save and close button not redirecting to parent record

Hello,

I took this piece from a thread months ago that was never answered back to, I am experiencing the same problem:

Problem: 
From the parent record a child record is added. When users just save and close the newly created child record they are redirected back to the parent record, but if they use the native save and keep working button, then later use the native save and close button, they are redirected to a view mode of the child record they were editing instead of being redirected back to the original parent record.

If this cant be fixed in quickbase what is the work around?

Please help, thanks

------------------------------
Mackenzie Phillips
------------------------------
Buttons
Relationships
  • BlakeHarrison's avatar
    BlakeHarrison
    Qrew Captain
    5 years ago
    The landing page is maintained in the breadcrumbs of the URL the user follows to get to the current form. If they use the 'Save & Keep Working' button, the breadcrumb changes to the current form, since it is the last page that was viewed before the button-click. The only way that I know of to allow this action and still allow the user to close and be redirected to the Parent would be to create a custom 'Save' button that saves and redirects to a specified URL like this:

    "<a id='saveButton' class='Vibrant Success' onclick='DoSave()' 
href=" & URLRoot() & "db/" & [_Parent DBID] & "?a=dr&rid=" & URLEncode([Related Parent]) & ">Save Changes</a>"​


    ------------------------------
    Blake Harrison
    bharrison@datablender.io
    DataBlender - Quick Base Solution Provider
    Atlanta GA
    404.800.1702 / http://datablender.io/
    ------------------------------
  • JimHarrison's avatar
    JimHarrison
    Qrew Champion
    5 years ago
    What my long lost cousin Blake says is true.  (no we're not related, at least I don't think we are... :P )

    Alternative:
    If the User is going to Save & Keep Working, open the new record in a new tab or window. When the User is done with the record, close the tab or window and return to the previous (parent) page.

    Downside, the User must refresh the page to see child record changes but you don't have to try to hide the Save Button using magic.

    This is right at the edge of Quickbase - Custom Pages wilderness. In JavaScript you can use the window.location function and parameterize the parent rid. Check Mozilla MDN, HASH and strip. Write a page in the Code pages area, then you don't have to "hide" the Save button.

    Jim


    ------------------------------
    Jim Harrison
    ------------------------------