Forum Discussion
- QuickBaseCoachDQrew CaptainOne solution is to create a dummy form with no fields on it. Then, in forms usage assign that form to be used for Grid edit for that report. So the user will be able to grid edit, but it will be an unsatisfying experience as they will have no columns on the grid. You might reinforce that with a note on the form.
- ElenaLarrabee1Qrew CaptainWell, except wouldn't that then also affect that report if I set it to be grid-editable on that form? I do want users to be able to grid edit reports when they're editing the form, but I just don't want them to be able to leave that form to go to the full child report.
Is there a setting I'm missing somewhere that would hide those options? - QuickBaseCoachDQrew CaptainHmmm, I don't know a solution to that nuance.
- DanLadner1Qrew TraineeYou can hide all of those options ("Full Report", "Grid Edit", etc.) using IOL--just place the following in a formula rich text field on the form, replacing "DBIDHERE" w/ the DBID of the child table (the one whose records are being displayed in the report link):
"<img qbu='module' src='/i/clear2x2.gif' onload=javascript:$(\"table[qbdbid='DBIDHERE'].ToolbarTable\").closest(\".Toolbar\").hide();>"
- ElenaLarrabee1Qrew CaptainDo you know if there's a way to leave the more > print option?
- DanLadner1Qrew TraineeMost likely it can be done, but I don't have the code for that, and it's not code I can come up with myself. Sorry!
- ElenaLarrabee1Qrew CaptainThat's all right, thank you anyway!