Deleting Orphaned Children (records)
Hellos, I have a scenario where I have a table where orphaned children exists , they can be recognised visually from hyperlink (See Screenshot). The question is how to filter for them so they can be deleted in QuickBase . I can do this easily outside of QuickBase but how to do this natively ?
Best ways get up to speed on the structure of an existing Quickbase business app?
I need to get up to speed on the structure of an existing QuickBase business app that has 40+ tables. Then, move it over time into a managed design cycle. Any suggestions on ways to do this? Or been here, done that? Thanks! Keith I'm coming from perspective of small business CTO wanting to bring our app into a managed development structure. Coding-wise, coming from Visual Studio and compiled code dev. I'm new to QuickBase. I confess to a feeling of frustration as I browsed the app in the QB design tools. Perhaps because of an expectation to be able to see the structure and dependencies of our app called out in a taxonomy of sorts. Or, be able to export the structure to bring into outside tools. Just noticed the QBL - it sounds promising.
Client portal/App setup help
I would like to create an app that is specific to a Client, I can use paid seats for the users logins. Specifically, there are 2 main functions I need. The ability for submission of request and then once reviewed, the ability to view/access the requested information from the Client specific App. I do not want to give any access to our main application, which is why I was thinking the client specific app would be best to build. I want to set the new app up similar to a “portal”, where this Client can log in and do/see several things such as: Submit an estimate request through a form Check the status of this request Provide updates for the request Add authorizations and scheduling updates Send message or make notes Upload attachments I am thinking I could create tables in the Client App that will mirror the tables/fields etc. that are in the main app, thus assisting in relating the data. Then have some type of notification set up when a new submission is made. Our teams would then review any new submissions etc. prior to using a pipeline to import the information into our main app. Once we have reviewed and approved the data in our main app, then I would like to have the client app updated to reflect the “same” details. I know this is possibly, I am just not sure the best way to set it up. Does QB have any prebuilt apps like this I could customize to our needs??? Any suggestions are appreciated!!
Moving data from a columnar table to a record based table
Not sure that's a great title, but it's the best I could come up with right now. I created the below table for ease of end-user data entry. (To increase adoption rate and reduce pushback.) I would like to create fields/or a table, that would basically take the column headers and the associated numbers into the more useful table that has a multiple choice field for offense type, the date and # in the column. I believe this is very doable, but I am just drawing a blank tonight.
