Start Audit Date
I need assistance with setting up a formula field where it captures an audit date when the status changes to “Awaiting Corrections.” The date should be recorded on the day the status changes to “Awaiting Corrections” and should remain unchanged even if the status later changes to “Validate Corrections” or “Completed.” For example: If the status changes to “Awaiting Corrections” on 11/08/2024, the audit date should be 11/08/2024. If the status changes to “Validate Corrections” or “Completed” on 11/09/2024, the audit date should still remain 11/08/2024. The audit date should only be set based on the initial change to “Awaiting Corrections” and should not update with any subsequent status changes. Could someone provide guidance on how to achieve this using formula fields?
Missing NetSuite Custom Fields
Missing NetSuite Custom Fields and details from purchase order line items when connecting from a QuickBase Connected Table I have a QuickBase app connecting to NetSuite through a QuickBase connected table. I managed to get the PurchaseOrder data from NetSuite, but I also want the line item details from those purchase orders and I can’t find a way to get the data from the line items. Anyone knows if I am supposed to be able to pull line items details directly from the purchase order? Or do I need to create a second connected table to some line items table in NetSuite? If yes, which table is it in NetSuite? I also created custom fields in NetSuite, but NetSuite custom fields don’t show up in the QuickBase “fields available from connected table” when configuring it in QuickBase. Is it normal that NetSuite custom fields don’t show up in QuickBase connected table configuration? How can I get NetSuite custom fields in a QuickBase connected table? Thanks in advance,
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?
