ContributionsMost RecentMost LikesSolutionsRe: Multi-Select Fields with Commas in Pipelines This is definitely an issue. I thought I put in a case for it, but I could not locate it in my history. To work around the issue I used a Quickbase Make Request step to do an API_ImportFromCSV. In that payload I could put the value of the multi-select into a set of quotations so that it would not break it up when inputing it in the new record. In the code sample below, the field "core value" is what had the issue similar to yours. <qdbapi> <usertoken>%user.token.xyz%</usertoken> <apptoken>apptokenhere</apptoken> <records_csv> <![CDATA[ "{{a.comment}}","{{a.core_value}}",{{a.cust_emp}},"{{a.emp_name}}",{{a.id}},{{a.dbid}},{{a.from}} ]]> </records_csv> <clist>7.9.6.8.11.13.10</clist> </qdbapi> -Sharon Re: Qrew Tip #01: How to Bulk Edit Report Columns This is a good reminder! Many Quickbase old timers (or those who've use it infrequently over the years) may not be aware that the multi-select and drag options were even added. Back in the olden days we only had the arrows 😜 -Sharon Re: Qrew Legend Finalists Named - Voting Open Through 3/14 🥳🥳🥳 Very excited to have made the cut with this group of fantastic Quickbase Qrew members! -Sharon Faust Re: [Snippet]Weekly Updates Excel Sheets to QuickBase Love how you've incorporated HTML, images, and mini tables! Keep up the good work. -Sharon Re: Record Picker in Grid Edit I find you have to be very fast to get to include a second or third character. So CDV would need to be entered all together very fast to jump to that entry... but it is possible. You are correct that you can't set a report to use for the record picker in Grid Edit or make it behave like forms where it searches the list. That may change when they release the new "Spreadsheet Edit" functionality (to eventually replace Grid Edit), but that isn't available yet. More on it should be shared at Empower at the end of the month. -Sharon Re: How to color code a table based on a forumla field? This should do it var number DR = -(ToDays(Today() - ToDate([Due Date]))); If( $DR = 5,"Red", $DR > 5 and $DR <= 10,"Yellow", $DR > 10,"Green", $DR < 0,"Purple") You can also replace the names like "Yellow" with a hex code like "#FDFD96" if you find the named color is not the best shade. Just be sure to include the pound sign. -Sharon Re: API Edit mobile forms Is this still an issue? If so can you post the full formula? I only see the two variables for "Approve" and "RefreshPage", so the issue may be in the rest of the formula where these variables are used. -Sharon Re: OAuth 2.0 While a lot of services require all of that Quickbase does not. If you wanted to send the data from the other service into Pipelines (trigged when the other service sends a payload) use the "Webhooks" channel. It will run based on the permissions of the Pipeline owner. If you are not using Pipelines and are directly sending data to Quickbase via API, each API will have different requirements for a user or app token that is included as part of the URL or headers. So no Client ID, Secret Key, or Scopes. Here is more info on the APIs. JSON RESTful APIs HTTP APIs -Sharon Re: Summary report & adding a total between grouping Unfortunalty it is not possible with Summary Reports. A simple workaround is to have multiple summary reports on a dashboard where each is filtered to 1 Salesroom and maybe a total summary at the bottom of the page that isn't broken out by Salesroom or Date. The other option is to add a a Summary table. What this would look like for your use case is a new table in your app (let's call it "Monthly Metrics"). Where you would have a field for Salesroom and Sales Date. This Monthly Metrics would be a parent table to the table where the data is. Each month you can have a pipeline to create the new month record for each Salesroom and link any matching children (or children can be matched to a month as they are added). Now you can add standard summary fields to the relationship for each of your totals. Your report would then be a Table Report with custom grouping to get the subtotals. It's a lot more work this way, but it does give you a nice clean report with subtotals. -Sharon Re: Kanban records per column limit 300 is a lot to manage on a Kanban, but it sounds like you really want the drag/drop functionality of a Kanban (vs simply using a table report). What I would recommend is similar to #4 in this Kanban Hacks post https://www.quickbasejunkie.com/blog/how-to-kanban-hacks Basically, have an 'order' parent and on it include 3 Kanban reports. The first for line items 1-100 items, the second for 101 - 200, and the last for 201 - 300. You may need to devise a new field to number the items 1 through 300 to use in the report filters, or perhaps that can be included in your CSV import. -Sharon