JustinTorrence1
Qrew Member
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Remote - Associate Quickbase Developer II
@Samir Agrawal My entire team is remote at the moment so I am very comfortable with having remote employees, there will never be a need for any of my team to visit a local office. Unfortunately, the states I listed are the only ones I am only currently approved to hire in and must comply with company policy. If we expand that list in the future I will make another post here. Thanks, ------------------------------ Justin Torrence Logical Position ------------------------------2Views0likes0CommentsRemote - Associate Quickbase Developer II
Hey Quickbase Community! I'm looking for someone to join my team at Logical Position. Apply here if you are interested and work/live in one of the following states: · Oregon ·Colorado ·Idaho ·Illinois ·Indiana ·Kansas ·Louisiana ·Missouri ·Nevada ·New Jersey ·Washington ------------------------------ Justin Torrence Quickbase Developer Team Lead Logical Position ------------------------------14Views0likes3CommentsRe: How to break up cross-app relationships
Judging from your screenshot of the webhook, it appears that you might have created new fields to hold Record ID#, Record Owner, and Last Modified By (9, 10, and 11). This means we can probably assume that you have changed the Key of the table so that the relationship can work. I think we must also assume that this relationship is not bi-directional as we know from my previous comment that built in fields cannot be overwritten (except by stored imports). If this is the case, what happens when a user needs to add a new parent record before selecting it in the child record? Must they first go to the source app to add the new record and then trigger the webhook? This seems like poor user experience, as the user would have to know that a record must be added to the source appbefore they create the child record and if they didn't do it in that order, they would need to refresh in order to see the record (created via webhook) show up in the record picker.5Views0likes0CommentsStatic Quick Base User Name
I have a connected Quick Base table that pulls from another application table containing "Employee Profiles". I have set the key field of this connected table to aQuick Base User field (This comes over in the connected table as text type instead of user type). I then have a formula field that that converts that text to a User type "ToUser([User])". The problem is, any time a user updates their email or their username, the Quick Base User (key) field is not updated with it. That, and any records that use this connected table as a parent lose their reference. So I am in need of a way to get a text or numeric (unique) "User ID" that never changes that I can convert to and from User type using a formula. Should I lock down the user preferences menu and manually assign usernames to all new users? Or am I completely overlooking something much easier. ------------------------------ Justin Torrence ------------------------------Re: How to update a default (canned) report with a custom field?
I think you are talking about Dynamic Filters? (The Element on the left sidebar of a report that allows you to filter data on the fly) There is a section in the report builder called "Filters", and a subsection in there called "Dynamic". Switch the radio button to "Custom" and you can select all of your own Dynamic Filters. Some fields cannot be used as a dynamic filter. There is a chart at the bottom of this page that shows you what kind of fields can be used as a dynamic filter:https://help.quickbase.com/user-assistance/dynamic_filters.html3Views0likes0CommentsRe: Multi-Select Text to UserID
Could you use a "User - List" field? If not, you will need a formula field that maps first names to users, then puts them into a list. This will need to be updated every time you want to support another user. Also, you will have to find a solution if a user with the same first name is added.0Views0likes1Comment