Recent Discussions
How to display related field value from a grid edit dropdown selector (rather than record id#)
I have a grid edit table report that requires the user to select the "Related Content Allocation" before editing the rest of the columns/fields. However, the dropdown is displaying the related field's record ID, which isn't very user-friendly. Is there a way to display other related field values in this dropdown rather than the record ID# easily? ------------------------------ Matt Makris ------------------------------
How to add a link to new notifications?
Does anyone know how to add a link to new notifications? In old notifications you can simply make a rich text link and reference the field, but in the new notifications it just shows the rich text field as text. My use case is: The notification fires from a child record, but I want to be able to have a link to the parent record in the email.
Summary report cross tab sort?
Working in a Business management app of multiple companies with all their job info/history. Have created a summary report showing monthly revenue and GP %, with the columns grouped by month so the total rows are YTD totals for each customer. Is there a way to make it only display top 15 customers? It is auto set to alphabetical with sorting disabled because of the cross tab sort... Ideally i could sort them high to low by the YTD total rows, but it is not an option. Any ideas how to navigate this? Some companies have 100+ customers so it looks horrible as is.Display a code page within the Quickbase interface
I have a Projects table, with a button in the form which opens in a new tab a single page application contained in a code page. The link looks like this: https://realm.quickbase.com/db/abcdefgh?pageID=17&projectId=81902&a=dbpage The &a=dbpage was added so that the code page loads wrapped by the Quickbase applicaton interface (with the tables in the left navigation and the header at the top). Recently I noticed that this doesn't work any longer and the page opens in a blank page. Is there a way to fix this?
New Forms - Editable Embedded Report
Hello, Does anyone know if they've released similar functionality to the legacy forms that allows editing embedded reports? We have a new form that needs a child relationship to capture n-records. The problem is that this record creation is available to EOTI and they should only be able to Add Records, not View or Edit. In other words, if they navigate away from the record they're creating (parent) to create a child they'll never be able to get back!
Conversion from user identifier to UserList
Hello, Has anyone found a more elegant solution to the problem of a list of user identifiers like ID's, usernames, emails, and casting or converting it to a UserList data type? I have found people mentioning a variation of the brute force approach which is essentially what I use. I have a count and conditionals to try to reduce needless processing. My total runtime is 0.073 seconds. ToUserList( If([Related Users - Count of Viewer Users] > 0, ToUser(Trim(Part(ToText([Related Users - View Access]), 1, ";")))), If([Related Users - Count of Viewer Users] > 1, ToUser(Trim(Part(ToText([Related Users - View Access]), 2, ";")))), If([Related Users - Count of Viewer Users] > 2, ToUser(Trim(Part(ToText([Related Users - View Access]), 3, ";")))), If([Related Users - Count of Viewer Users] > 3, ToUser(Trim(Part(ToText([Related Users - View Access]), 4, ";")))), If([Related Users - Count of Viewer Users] > 4, ToUser(Trim(Part(ToText([Related Users - View Access]), 5, ";")))), If([Related Users - Count of Viewer Users] > 5, ToUser(Trim(Part(ToText([Related Users - View Access]), 6, ";")))), If([Related Users - Count of Viewer Users] > 6, ToUser(Trim(Part(ToText([Related Users - View Access]), 7, ";")))), If([Related Users - Count of Viewer Users] > 7, ToUser(Trim(Part(ToText([Related Users - View Access]), 8, ";")))), If([Related Users - Count of Viewer Users] > 8, ToUser(Trim(Part(ToText([Related Users - View Access]), 9, ";")))), If([Related Users - Count of Viewer Users] > 9, ToUser(Trim(Part(ToText([Related Users - View Access]), 10, ";")))), If([Related Users - Count of Viewer Users] > 10, ToUser(Trim(Part(ToText([Related Users - View Access]), 11, ";")))), If([Related Users - Count of Viewer Users] > 11, ToUser(Trim(Part(ToText([Related Users - View Access]), 12, ";")))), If([Related Users - Count of Viewer Users] > 12, ToUser(Trim(Part(ToText([Related Users - View Access]), 13, ";")))), If([Related Users - Count of Viewer Users] > 13, ToUser(Trim(Part(ToText([Related Users - View Access]), 14, ";")))), If([Related Users - Count of Viewer Users] > 14, ToUser(Trim(Part(ToText([Related Users - View Access]), 15, ";")))), If([Related Users - Count of Viewer Users] > 15, ToUser(Trim(Part(ToText([Related Users - View Access]), 16, ";")))), If([Related Users - Count of Viewer Users] > 16, ToUser(Trim(Part(ToText([Related Users - View Access]), 17, ";")))), If([Related Users - Count of Viewer Users] > 17, ToUser(Trim(Part(ToText([Related Users - View Access]), 18, ";")))), If([Related Users - Count of Viewer Users] > 18, ToUser(Trim(Part(ToText([Related Users - View Access]), 19, ";")))), If([Related Users - Count of Viewer Users] > 19, ToUser(Trim(Part(ToText([Related Users - View Access]), 20, ";")))) )
Why Quickbase? Why?
One of the few things I ever said that Quickbase lacked was design capabilites, particularly in form design, and when I saw that they were making changes to that I was pumped. Now that I have used it a bit, I am scratching my head... Although I do love some of the options they have added, why would you take away things like being able to have the field label on the side or on top? And the addition of columns was great! But why take way the ability to have a couple small fields still be able to be on the same line within those columns? I'm trying to mimic a form that is currently in Excel and the section that currently only occupies only about a 3rd of the page, a user will have to scroll down to finish entering all the info because of the spacing. Am I missing something or does forms design still need some work?
