Numeric Fields Show Separator After 4 Places
Curious to get other's thoughts. We have not enabled the new Grid Reports in our primary application. We have one application used by a small group that does have new Grid Reports enabled. This application (with Grid Reports enabled) has summarized data from our primary application. I was updating the data today and noticed the totals have the comma separator after 4 places. So, 100000 is displayed as 10,0000. When last updated, I'm pretty sure the comma separator was after 3 places. I see in the field properties a select of Show separator after 4 places or Show separator after 3 places. This appears to be a new option with the default of 4 places. For all the numeric fields, I'll need to manually change to 3 places. I could not find anything in the release notes about this option. Has anyone seen anything related to this? Is there any way to change the default to 3 places? I have a feeling this is going to be overlooked quite a bit when adding new numeric fields.
Search Feature
I'm trying to create a search feature where a user can search for let's say John Smith or a Tax id or PIN. For the standard search, if the user searches for John Smith, it does not return any records, even though there is a John Smith. I'm assuming this is happening because the first and last name are in different fields. I kind of want an ai search but only search one table and any fields or combination of fields in that table. Is this possible?
Thank You!
A quick note to say thank you to all who attended the QB Leadership AMA today! Not just for attending but for engaging and being honest and transparent in your comments and questions. The more feedback we have the better we can become. The entire executive leadership team believes feedback is a gift and we thank you for sharing. Although we'll never be able to action all the feedback, we are always ready to listen and provide and honest response and action what we can. It's an exciting time at Quickbase as we continue to transform; continuing to put you, the customer, at the center of everything we do, evolving of our products to solve real business problems and setting our sights on ensuring you're deriving value from your investment. Your partnership is what has made Quickbase stronger over the last 20+ years. Without you, we don't exist. Thank you!Sam Trachy's Daily Office Hours 1pm EST
Quickbase Solution Consultant SamTrachy offers an Office Hours to anyone in The Qrew to join! This is a great resource even if you don't have a question and want to join and listen in. All questions are welcome! Beginner, Intermediate, Advanced, it doesn't matter. Whatever Quickbase question is on your mind, bring it to Office Hours and go over it with a Quickbase Pro. Sign up for as many Office Hours sessions as you like here!Any performance issues with connected tables?
I posted this about two years ago regarding performance issues when using cross-app relationships: cross-app relationships and performance We ultimately ended up not sharing data between the apps. But does anybody know if connected tables have the same issue? Meaning using a table in one quickbase app connected to a table in a different quickbase app. My guess is that regardless of the source app, the "connected" part is implemented via an internal script copying data from the source table to the target QB table. And that would also be the case even if the source was another quickbase table. Has anyone run into performance issues when using connected tables between QB apps? thanks!
