Formula URL button - save and redirect
Hi there I?ve created a form accessible to ?everyone on the internet? for our clients to submit service requests. I added ?&ifv=20? to the url to hide the qb branding. However, doing this causes the...
Forum Discussion
Try my suggestion, it�s stupid simple.
Hi,
None of these suggestions works in my case. Any help is greatly appreciated!
I'm in the edit mode for a record that already exists. I need to save the current record which triggers certain form rules and automations and then I want to redirect back to the parent record on a specific form. Is this possible?
None of these suggestions works in my case. Any help is greatly appreciated!
I'm in the edit mode for a record that already exists. I need to save the current record which triggers certain form rules and automations and then I want to redirect back to the parent record on a specific form. Is this possible?
- MarkShnier__You
Qrew Legend
I think this is an easy one
Go to the child table and Advanced Properties and check the box for
Save parent record automatically when a child record is created
Then just make a URL formula link to go to the parent record in edit mode.
URLRoot() & "db/" & [_DBID_Parent_Table_Alias] & "?a=er&rid=" & [related parent]
Then when you click that link to navigate away from the child which has been "dirtied" with unsaved input, Quick Base will auto save and then go to your link.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- Oh wow! That was a super simple solution and it worked. So that option enables 'the child' to be saved and go back to the parent in spite of the help text being misleading and saying --> "Select this option to automatically save a parent record in a parent table when a child record is created. You will not be prompted to save the parent record. It is automatically saved."
But I just came across a limitation with it, what if the record is not being 'dirtied' by the user but a form rule is supposed to dirty it.
Previously the user has two button choices that takes them to two separate forms (Approval Form and Rejection Form) for the same record and on these pages, they have the option to add notes if they're approving the request or rejecting the request. For the rejection of the request Notes are required; for approval Notes are not required. So it works when the user is rejecting it (because by adding notes, the user dirties the record) but it doesn't work when the user is approving the record and does not put in notes because they're optional. Both forms have a form rule trigger that changes the approval status on save.
Thanks a lot Mark!- I was able to figure this limitation out.
I changed the Approval button from a simple redirect to an API_Edit record and then timestamp a hidden field. A form rule then wipes the hidden field when it is not empty on the Approval form thus causing the record to be dirty and the save to work even when the notes are optional on the Approval form.
Thanks again Mark for your idea!
------------------------------
Rohit Burani
------------------------------
