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!!
Changing date field properties
I have to change a date field from it's current state: automatically populated from a calendar event sign up, to a new state: manual entry. This field is in reports, pipelines, rules, etc. Will there be fallout from this change? Additionally, I have to change another date field from manual input to formula driven based on another field's selection. Will there be fallout from this change as well?
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 ?APP - Communications
I would like to create an APP to manage my field teams in the construction of fiber optic networks, also the entire project such as allocation of maps for teams, production information, finance, control of tools and expenses such as fuel. Este é o meu primeiro contato com quickbase, gostaria de saber se existe uma maneira de encontrar um freelancer que possa fazer isso por mim. Para o relatório diário das equipes que já utilizo o FastField, uma integração entre as plataformas seria interessante também Obrigado
Copied Field doesn't have the same usage as the original
I created a check box field and it's currently used in 7 forms/reports. When I copied it to add in another area of the same form it shows as only being used in 2 forms/reports. How can I add it to the additional areas I need it in? I want the copies to function the same as the original. I attached screen shots of the original and the copy. Thank you!!Quickbase - Jumping into managing someone else's build-out
Hi all! I'm just looking for some beginner/intermediate wisdom. I am taking on the (to me, much coveted) task of managing and revamping Quickbase across other arms in my division. This'll be the true test of whether I'm actually cut out for this haha - it's one thing to be self-taught and know how to build and fix across the empire thatI'vebuilt, but another to jump into someone else's empire. So. Looking for some wisdom: What things should I know when going in and offering up a "revamp" of sorts? What major pitfalls should I watch out for? How might one approach doing this sort of thing? My first approach has been to learn about what sorts of things they use Quickbase for today, what data is captured, what they'dliketo use it for down the line, and then with that, I'm peeking in the back end, seeing what fields/forms/reports exist, and wrapping my head around how it all is (or isn't) working together today A sub-set of questions - might it behoove us to build several apps? I honestly have no idea how much Quickbase costs our organization, if it's per app, per user, some combination. That all is tightly managed at a level higher than me in our IT department, and app managers are only that - we're not "App Owners". But I've been thinking it really might behoove us to have several apps, that are all cross-linked, because for instance, each unit in our division coudl really have several tables -- as my unit does. There are things that will be division-wide, such as inventory management; but if we lump all these tables into one app, it will get pretty messy pretty quickly. So my sense is the best thing to do would be propose having several added apps that can be connected, one "Master" app where the universal tables live, and one for each division's division-specific work.
