ContributionsMost RecentMost LikesSolutionsRe: Exciting feature for integrators Ð new mergeFieldId in API_ImportFromCSVPersonally, I?d just use a Service Worker.Re: Sneak Peek: Type-Ahead Search Picker@josh and @mark, Open support tickets. Our team can help figure out what's going on. Sam Jones Quick Base Product Manager Re: Sneak Peek: Type-Ahead Search PickerIf they're seeing the record ID, it's likely set as the field to be displayed on the form, so in the old setup, they would see Record ID on the View mode, and the pick list on the edit mode. We're trying to get View and Edit more aligned if they're both based on the same form.Re: Sneak Peek: Type-Ahead Search Picker@Mark/ Quick Base Coach, Yeah, I'm concerned about breakage too. We're thinking about making a special exception: If the single field which would be displayed is the Record ID#, then appending the second field from the picker, which would likely be the identifying value. Sam Jones Quick Base Product Manager Re: Sneak Peek: Type-Ahead Search Picker@Mark/ Quick Base Coach, If that's the field which is on the form, shouldn't it be the field which is displayed on the selected value? When I started using Quick Base I found that having a value which wasn't the one on the form displayed very confusing. Sam Jones Quick Base Product Manager Re: Sneak Peek: Type-Ahead Search Picker@Alex, We've got a fix for clearing values coming in the next release. Sam Jones Quick Base Product Manager Sneak Peek: Type-Ahead Search Picker While we at Quickbase love to work on great new features, like Kanban reports or Automations, we also take time to focus on the fundamentals. And what could be more fundamental to Quickbase than quickly and accurately entering data? So many of our customers tell us they come to Quickbase apps because they've outgrown spreadsheets and need to move to a relational database to handle the complexity of the work they need to track. Recently, we've been taking a hard look at how we can improve this fundamental activity of Quickbase apps: relating data. What did we find? After talking to customers with big data sets and small, we realized our record picker needed to be better at finding records quickly and making sure users knew exactly what record they were picking! If you're not familiar with our record picker, here's a crash course. (You can find out more about configuring it in Quickbase University.) When you're working with a relatively small data set, we show a simple HTML drop down. It works well if you've got some easily discernible records and you know what you're looking for, but if you've got a larger set of data, it can be much harder to find what you're looking for. Now, one of the things we all love about Quickbase is how deeply customizable it is. So what if I want to only pick from records which meet a certain criteria? Or if I want to make sure the most likely to be picked options are at the top? Quickbase has a solve for that! In the form properties, you can choose a report on which to base the record picker, which allows you filter and sort the field. It's great that you can apply sorts and filters, but unless you really trim down the columns, it can be really hard to read for end users. Beyond that, they may not understand what data is displayed in the list and given that each record displays all its data on one line, it can be hard to match up values to compare them. In addition, our users told us they expected to search through these records to find what they were looking for, but our simple record dropdown doesn't support that. For search, we need to go into the record picker pop-up. In field properties, you can configure this relationship to always use our record picker pop-up but getting to it requires more clicks and takes the user out of the context of the record they're editing. What we found in talking to customers was that their teams needed a faster way to search their data. After seeing all this, we got to work. Presenting the new Quickbase Type-Ahead Search Picker: If your app builder has chosen to display only one field to pick records on, we're now going to present a fast, searchable picker, very much like the new field picker we rolled out back in spring or the user picker we've have. If your app builder has chosen a report or the standard record picker to select from, you'll see a multicolumn picker, able to display up to nine fields of relevant data, with each column labeled so users clearly can see what they're picking from. We load the first 50 results automatically, so users can browse. As you search, the list updates in real time, pulling in more records and highlighting the matching terms, very much like our user field type. This new picker will be rolling out to all users in the coming months. If you'd like a sneak preview, we have it available in early access starting the week of September 24th. Just have your realm administrator open a support ticket and request it at https://login.quickbase.com/qb/support/listcases Thanks for reading and be on the look out for more posts and previews about our new type-ahead search picker! Sam Jones Quickbase Product ManagerRe: How do I track changes users make on my kanban boards?Thanks for posting this Brian! I love seeing all the great things which can be built combining automations and Quick Base's user interface! Sam Jones Quick Base Product Manager Re: Kanban group by related recordAlex, For what it's worth, it's a feature I'd love to build. I need to be getting consistent feedback in favor of it to justify my developers building it out, so I'd encourage you to post it to uservoice and ask your colleagues to vote for it over there. Sam Jones QuickBase Product Manager Re: Group Kanban cards by userHey Daniel, You've got two options: 1) wait till August 19th, when we'll release this feature natively. or 2) Create a Multiple Choice field with the values being user names, then create a formula user field on your form with the formula ToUser([Multiple Choice Field]) in it, which will let you do user based reporting and permissions from the value set on the Kanban board. Personally, I'd wait the 10 days. Sam Jones QuickBase Product Manager