Button in Embedded Report
Is it possible to have a functioning button in an embedded report? One per row/record. Due to circumstances, I have an embedded report that facilitates mass input of data. But for things to work...
Forum Discussion
Evan,
Thanks for the very detailed response. I very much appreciate it. Sorry for the delayed follow-up on my end. I have been on vacation for the past few days.
Yes, that is how I have the tables set up.
I understand how your Option #2 works, in theory. However, for it to work as you suggest, wouldn't the Work Order Record ID would first need to be generated? Meaning the work order would need to be saved so that it had an associated Record ID# first, before the automation can run, right?
With how the process flow works currently, generating the Work Order first, then manually going back in to edit it to click a button breaks the flow somewhat.
Also, if we set it up to generate a new child and grandchild record each time it was edited, we would have more children records than really are needed. The Grandparent record will be edited multiple times throughout the process, so we don't want to generate a child/grandchild record each time.
However, after reading through your suggestion, I had a thought, but am not sure if it will work.
Ideally, from within the work order form, if I click on "Add new Job", the code in the button would save the Work Order (thus generating a Record ID#), and then also generate a new job record, taking me back to the Work Order form in edit mode.
By doing it this way, I wouldn't need to worry about saving the return pat back to the Work Order from the Jobs form.
I have the code to save and keep working. It is currently in a Formula Rich Text button:
I also have the code to generate a new Job, take me back to the Work Order in edit mode. It is currently in a Formula URL button:
I was hoping to combine them both into a single button, so that it first runs the "Save & Keep working" and then generates the Job.
I tried the following:
However, when I went to combine them, I get an error message. I am sure it is due to my lack of experience in syntax and combining different coding types.
Any thoughts? Do you think something similar to the above would work? I am trying to make it as simple as possible.
------------------------------
Andrew
andrew.fry25@gmail.com
------------------------------
Thanks for the very detailed response. I very much appreciate it. Sorry for the delayed follow-up on my end. I have been on vacation for the past few days.
Yes, that is how I have the tables set up.
I understand how your Option #2 works, in theory. However, for it to work as you suggest, wouldn't the Work Order Record ID would first need to be generated? Meaning the work order would need to be saved so that it had an associated Record ID# first, before the automation can run, right?
With how the process flow works currently, generating the Work Order first, then manually going back in to edit it to click a button breaks the flow somewhat.
Also, if we set it up to generate a new child and grandchild record each time it was edited, we would have more children records than really are needed. The Grandparent record will be edited multiple times throughout the process, so we don't want to generate a child/grandchild record each time.
However, after reading through your suggestion, I had a thought, but am not sure if it will work.
Ideally, from within the work order form, if I click on "Add new Job", the code in the button would save the Work Order (thus generating a Record ID#), and then also generate a new job record, taking me back to the Work Order form in edit mode.
By doing it this way, I wouldn't need to worry about saving the return pat back to the Work Order from the Jobs form.
I have the code to save and keep working. It is currently in a Formula Rich Text button:
"<div class='Vibrant Success' onclick=$('#footerSaveAndKeepWorkingMenuOption').click();>Save and Keep Working</div>"
I also have the code to generate a new Job, take me back to the Work Order in edit mode. It is currently in a Formula URL button:
URLRoot() & "db/" & [_DBID_JOBS] & "?act=API_AddRecord"
& "&_fid_16=" & URLEncode ([Work Order ID#])
& "&rdr=" & Dbid()& URLEncode("?a=er&rid="&[Work Order ID#])
I was hoping to combine them both into a single button, so that it first runs the "Save & Keep working" and then generates the Job.
I tried the following:
"<div class='Vibrant Success' onclick=$('#footerSaveAndKeepWorkingMenuOption').click();>Save and Keep Working</div>"
& URLRoot() & "db/" & [_DBID_JOBS] & "?act=API_AddRecord"
& "&_fid_16=" & URLEncode ([Work Order ID#])
& "&rdr=" & Dbid()& URLEncode("?a=er&rid="&[Work Order ID#])
However, when I went to combine them, I get an error message. I am sure it is due to my lack of experience in syntax and combining different coding types.
Any thoughts? Do you think something similar to the above would work? I am trying to make it as simple as possible.
------------------------------
Andrew
andrew.fry25@gmail.com
------------------------------
Andrew,
Thanks for clarifying your use case!
A revised version of Option 2 might work:
You can set up Automations to fire on different conditions including "only add records" and "add or modify records". Additionally, any automation will fire after the record is created, so you won't have to worry about [Record ID#] not yet existing. With that in mind, maybe you could do something like the following:
Regarding the button:
Without getting too into the weeds, the code in your last message generates an error due to syntax. Formula Rich Text fields allow you to inject HTML code into native QuickBase, but you have to write all of the code. In Formula URL buttons, QuickBase wraps a URL link in HTML code for you. That's why URL based API Calls work in Formula URLs, but you have to wrap additional code around the URL based API call for it to work in Rich Text.
What you describe can be done, but it's a little advanced. If you want to go down that route, I would recommend researching how to embed JavaScript scripts in HTML code using jQuery (that's what the "$" indicates) and using callback functions in jQuery's "onClick()" function.
------------------------------
Evan Westbrook
PRIME Developer
Harder Mechanical Contractors Inc.
Portland OR
------------------------------
Thanks for clarifying your use case!
A revised version of Option 2 might work:
You can set up Automations to fire on different conditions including "only add records" and "add or modify records". Additionally, any automation will fire after the record is created, so you won't have to worry about [Record ID#] not yet existing. With that in mind, maybe you could do something like the following:
- Automation 1
- When "Work Order" Record is added, then "do stuff." No need for a button there unless you have use cases where child records are not needed.
- Automation 2
- When "Work Order" Record is added or modified and conditions are met, then "do stuff."
Regarding the button:
Without getting too into the weeds, the code in your last message generates an error due to syntax. Formula Rich Text fields allow you to inject HTML code into native QuickBase, but you have to write all of the code. In Formula URL buttons, QuickBase wraps a URL link in HTML code for you. That's why URL based API Calls work in Formula URLs, but you have to wrap additional code around the URL based API call for it to work in Rich Text.
What you describe can be done, but it's a little advanced. If you want to go down that route, I would recommend researching how to embed JavaScript scripts in HTML code using jQuery (that's what the "$" indicates) and using callback functions in jQuery's "onClick()" function.
------------------------------
Evan Westbrook
PRIME Developer
Harder Mechanical Contractors Inc.
Portland OR
------------------------------