ContributionsMost RecentMost LikesSolutionsRe: Convert comma separated values to new child recordsQuick FYI that Usertokens supersede Apptokens. You don't need an Apptoken if Usertoken is passed.Re: Ask Me Anything about Quick Base PerformanceHi Kyle. We offer a handful of tools to help you diagnose this. Here are a couple: https://help.quickbase.com/user-assistance/monitoring_performance.html https://help.quickbase.com/user-assistance/about_profiler.html We would encourage you to put in a support case with our Care groups. The more information you can provide us, the better. We can look at backend logs to see what is going on and make some recommendations to help you improve the app. For example, there may be opportunities to improve reports or form responsiveness. We also have a lot of content geared up for Empower. Will you be joining us? We even have a performance workshop where we will help you with your app live! Re: Ask Me Anything about Quick Base PerformanceHi Jonathan. We will post sessions and audio records here: https://university.quickbase.com/series/empower but I don't think there will be video. We have a handful of sessions around performance/scale at Empower. We also will be doing a deep dive into how Quick Base works under the hood. We have tables with thousands of fields (though we wouldn't encourage that without discussing with us first). Are you looking for information on optimizing your current app? Re: Ask Me Anything about Quick Base PerformanceHi Owen. Sorry you went through this. We continue to make investments under-the-hood. We have a lot to share about this at Empower and have also had a handful of improvements recently released. That being said, we are able to contribute to a fully scalable ecosystem. We put significant effort into this area. At the bottom of that article is a link to something our best practices team wrote on the best ways to share data. We see the most important part of preventing your situation as getting builders the right information early on in the process. The miss on our part was that you didn't have any of the information up front about cross apps and guiding principles around app structure. Cross apps are a powerful tool, but they force Quick Base to share resources because of our unique in-memory database architecture. So this is a trade-off we want to empower folks like you to make by having the right information to make educated decisions and we will be there to support you through the journey. Re: Ask Me Anything about Quick Base PerformanceAghh. Ok. So we have actually heard that users want this too, especially in finance/ops, similar to how those users interact with Excel and can step through the formula. I would also expect you would want this to work in _Test as Role/User_ as well?Re: Ask Me Anything about Quick Base PerformanceLove this idea. We already added the dependency diagram and have thought about different ways we could expose what you are looking for. There are a handful of challenges that are on the list here: Some admins do not want users to be able to see this. That means we will have to add a toggle, which introduces the concern of where that toggle goes. Form level? Table level? Behind the scenes, we are smart enough to not recalculate certain things until needed (there is a lot that goes into this decision on the fly) and so displaying that calculation needs some work in those cases. Would love to hear any other thoughts folks have on this.Re: Ask Me Anything about Quick Base PerformanceYep! We will be talking about this a little at Empower. In short, we want to expose much of what you have mentioned here to realm and/or app admins.Re: Ask Me Anything about Quick Base PerformanceHi Erin. We are focused on performance of Quick Base applications for this AMA, but I would love to offer some insight. Regarding the # of summary fields, I would suggest posting this on UserVoice (or voting if already there). We regularly have healthy debates about what we want to default for users. For those of you that want "# of..." automatically added, there will be many folks upset that we are cluttering their application! :). It is a common struggle and we try to root these decisions in experience, data and user studies. For "Use New Experience", what are you referring to specifically? We generally offer newer experiences for a limited period before transitioning fully to the new. This is important to ensure the reliability, consistency and our ability to support the platform. If you are having an issue, please open a Care case so the teams can look into it. Note that we _are_ working on a new way to manage your experience preferences for things like this, but wouldn't have a way for example to keep or force all users to a legacy experience. Re: Ask Me Anything about Quick Base PerformanceHi Jenni. By themselves, Automations are performant and we have put significant effort into improving the infrastructure and scalability of those over the past ~6 months. Since we use our own APIs as a best practice, we also have to consider the performance of the Quick Base app itself. That means designing the Automations carefully to not do something like add/modify/delete/copy huge amounts of records all at once while your application is heavily being used by users. While it is always good to design for performance, by and large, most people do not experience any performance issues in Quick Base, let alone in Automations.Re: Ask Me Anything about Quick Base PerformanceIntegrations in general are extremely tricky when it comes to performance. We have to tango with multiple things such simply server load as the other system's response time, API limits/pagination rules as well as our own. We are aware of some situations where there have been Sync issues with certain connectors and we have made improvements to those respectively. I'm going to ask someone to reach out to you to gather more details so we can look into this.