Forum Discussion
SimonH
Qrew Cadet
I think you are correct that there would be no way to grab the Weekly Plan record ID to embed in the button, as the button exists only in the context of schedule IDs.
You can however use a code page. In this case the button would direct to the code page with the parameter for the schedule ID as that is possible, then you can use JS to extract the weekly Plan ID from the referring URL, of course assuming that the button was clicked from within the weekly plan record page.
You can then have the code page either redirect to the New Planned Activities form with both values prefilled or actually have the code page create the record and then redirect to the new activity in either read or edit mode.
I've done something similar using combined buttons and code pages so if you think this would work for you let me know and i'll try to post a sample
------------------------------
Simon H
------------------------------
You can however use a code page. In this case the button would direct to the code page with the parameter for the schedule ID as that is possible, then you can use JS to extract the weekly Plan ID from the referring URL, of course assuming that the button was clicked from within the weekly plan record page.
You can then have the code page either redirect to the New Planned Activities form with both values prefilled or actually have the code page create the record and then redirect to the new activity in either read or edit mode.
I've done something similar using combined buttons and code pages so if you think this would work for you let me know and i'll try to post a sample
------------------------------
Simon H
------------------------------
JonFroderberg
3 years agoQrew Cadet
Hi Simon-
I'm quite interested in seeing an example! I'll share it with my team and hopefully we can arrive at something that will save our field personnel some clicks.
------------------------------
Jon Froderberg
PRIME Developer
Harder Mechanical Contractors
https://www.harder.com
Portland, OR
801.946.0576
------------------------------
I'm quite interested in seeing an example! I'll share it with my team and hopefully we can arrive at something that will save our field personnel some clicks.
------------------------------
Jon Froderberg
PRIME Developer
Harder Mechanical Contractors
https://www.harder.com
Portland, OR
801.946.0576
------------------------------
- MarkShnier__You3 years agoQrew LegendJon,
I am not sure exactly follow your question but if your situation is that you are sitting on a record and on that record are two embedded reports which are not related to the record you are sitting on, and you want something to happen when a button is clicked that requires knowledge of the record the user is sitting on then then I do have a solution which involves one click on the record you are sitting on.
That click would record the record ID of the record that you were sitting on in a user focus table and that information would be available to any other tables in the app. The concept could work for you it might save you from having to use code pages which are arguably more technical to maintain in the future.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------- JonFroderberg3 years agoQrew CadetHi Mark-
The embedded table for Schedule IDs is a report link where the records do not know the Record ID of the form/record on the screen.
The second embedded table for Planned Activities, those records are children of the displayed record.
I'm very interested in learning more about your solution as well!
------------------------------
Jon Froderberg
PRIME Developer
Harder Mechanical Contractors
https://www.harder.com
Portland, OR
801.946.0576
------------------------------- MarkShnier__You3 years agoQrew Legend@Jon Froderberg Contact me by email and I can give you a quick demo right now.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------