Forum Discussion
EvanMartinez
Quickbase Staff
Hi Nick,
Welcome to Quickbase and congrats on becoming a Quickbase Builder. If you are looking for some guidance on the process of Quickbase building a great resource would actually be Quickbase University. We have courses that focus on Orientation into Quickbase or App Planning that combine videos and text, you can even build along to pick things up or just jump to sections that cover topics of interest. You can also use the Exchange to grab example apps that already have forms, dashboards, reports, etc. built to see how others have created workflows and borrow ideas for pieces you like.
It sounds like a lot of the workflow you are looking for would have Transactions as your parent record and then Audits as your child records. Then you could use a related Transactions field that will pull down a list of Transactions that you can pick from that then populate lookup fields (fields of information pulled from Parent records that are read only and change when you change the related parent).
There is obviously more that goes into getting the exact experience that you are looking for as Mark mentioned, especially if there are some elements you really want to appear in a specific way. Even just watching a bit of University can help you get familiar with the key pieces of Quickbase and relationships and the terminology that is used in the platform. Best of luck with your building!
------------------------------
Evan Martinez
------------------------------
Welcome to Quickbase and congrats on becoming a Quickbase Builder. If you are looking for some guidance on the process of Quickbase building a great resource would actually be Quickbase University. We have courses that focus on Orientation into Quickbase or App Planning that combine videos and text, you can even build along to pick things up or just jump to sections that cover topics of interest. You can also use the Exchange to grab example apps that already have forms, dashboards, reports, etc. built to see how others have created workflows and borrow ideas for pieces you like.
It sounds like a lot of the workflow you are looking for would have Transactions as your parent record and then Audits as your child records. Then you could use a related Transactions field that will pull down a list of Transactions that you can pick from that then populate lookup fields (fields of information pulled from Parent records that are read only and change when you change the related parent).
There is obviously more that goes into getting the exact experience that you are looking for as Mark mentioned, especially if there are some elements you really want to appear in a specific way. Even just watching a bit of University can help you get familiar with the key pieces of Quickbase and relationships and the terminology that is used in the platform. Best of luck with your building!
------------------------------
Evan Martinez
------------------------------
NicholasWhite
3 years agoQrew Member
Hi Evan,
Thanks for your reply.
"There is obviously more that goes into getting the exact experience that you are looking for as Mark mentioned, especially if there are some elements you really want to appear in a specific way. "
The vibe I'm getting, that 'displaying a list of records as a sortable, filterable table; with radio buttons on the side to load a record into the form', is not possible out of the box.
I'm fortunate that this app was already built using a dropdown which gives the users the ability to select records; I'll go back to my boss to report that this will require more work than anticipated to get that dropdown to appear as a table with radio buttons.
Thank you,
Nick
------------------------------
Nicholas White
------------------------------
- MarkShnier__You3 years agoQrew LegendNicholas,
Just to chime in once again into this thread. If your boss is not happy with the current workflow and then imagines very particular user interface without really knowing what QuickBase is capable of than what you end up as a path towards custom programming that will cost ballpark $10,000. Anything can be done in JavaScript and it would use native QuickBase on the back into store the data and it before you know it it turns into a one-week project between the discovery phase at the beginning as to what you want and then letting a programmer or loose at it for two or three days and then presenting the solution to you and then they have to leave some room for UAT feed back (User Acceptance Testing).
But if you don't get so fixated on a very exact user interface and more focussed on the workflow you want then there's still a good chance you can get 95% of the workflow efficiencies that you want and have the advantage that it's done with a few hours of consulting time and all in native Quickbase which means that it will be more maintainable in the future.
So it's not like I'm pitching hard to score a big three hour consulting contract :). What I'm really trying to say is the trick with QuickBase is that you are given a set of native tools and the question is how can you put those tools together to give the best user experience possible. So if we focus on the workflow and less hung up on the very particular UI you may in fact be able to get the workflow you want.
Hence my original suggestion is to get on a call with you do some no charge discovery work to understand your desired workflow and then ballpark a small consulting project for you to accept or reject.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------