JoeHargrave
Qrew Trainee
Joined 6 years ago
User Profile
User Widgets
Contributions
Limit Dropdown Choices from Reports
I feel like I'm missing something easy here.... In a form, when using a dropdown selector for records from any table, I can limit the choices to be based on filters in any report, among other easy methods. However, in a report or grid edit report, when selecting a record in grid edit, I can't find a method to limit that selection to certain criteria, based on that specific report. Can this be done? ------------------------------ Joe Hargrave ------------------------------63Views0likes1CommentTask Due Date via Formula Date
I'm automating the creation of a task list with Pipelines. The various tasks are due on formula dates - and I've created the necessary formula date fields I need. (These are subtractive formula date fields, based on a date already in the record, minus # of days). So I have a few of these formula date fields that give me the needed due dates, but I hit a bit of a roadblock when building the pipeline. When I create a record for the tasks table, the 'due date' selection is a calendar, and I can only pick a specific date. Since the list of tasks needs a few different due dates, I can't figure out how to get my due date to be the appropriately chosen due date since Formula Dates can't be used in Pipelines. I feel like I'm missing something simple here. If I need four tasks created, each with a different due date (that is a subtraction of days from an existing date), what's my simplest path here? ------------------------------ Joe Hargrave ------------------------------54Views0likes3CommentsRe: New Dashboard versus old Home Page - and Mobile App Usage
Thanks Mark! That was kinda what I was thinking too. And maybe the mobile is going to a default dashboard instead of the most recently assigned home page. I think it was coincidentally the same thing when I was playing with it. All makes perfect sense though. ------------------------------ Joe Hargrave ------------------------------46Views0likes0CommentsNew Dashboard versus old Home Page - and Mobile App Usage
I have found a little 'perk' that may be inadvertently adding a new feature I've wanted for a long time. I've been looking for a way for quite some time, to have different dashboards or home pages for mobile versus computer. Since it seems the new beta dashboards are not opening on the mobile app, I've just gotten the ability to do what I need. It appears that the mobile app uses whatever home page was assigned to a role prior to assigning a new dashboard as the home page for that role. So I can set a home page for a role, to an existing home page that I've edited for mobile use. Then, if I create a new dashboard as the home page for the role, it becomes the home page on computer, but the mobile uses the previous home page. This is awesome! But, does anyone know if this is intentional, or if it will continue to behave this way if/when new dashboards become mobile friendly? I would love to build old home pages for mobile and new dashboards for computer, and assign the roles accordingly. But I don't want to lose what I've done once the new dashboard becomes mobile friendly, if it ever will. Just thought someone here might have some insight on this. THANKS ------------------------------ Joe Hargrave ------------------------------31Views0likes2CommentsFormat Rich Text - Formula
I'm embarrassed to admit the amount of time I've spend attempting to do this without bothering anyone... smh. I'm missing something really elementary here. I'm simply trying to concatenate a few fields of data into large, bold text. Here is the basic concatenation in a rich text - formula field: [Entertainment Coordinator - Staff Member - Full Name] &" | "&[Entertainment Coordinator - Staff Member - Email] &" | "&[EC Cell Phone] That works perfectly for assembling the information as needed, into this output: Mike Duane | mike@onefivesixfour.com | (469) 359-0203 Now, I need that output to be GIANT, and bold. If possible, I'd also make it #6e3686 (color). I know it should be simple, but I'm striking out. Any help would be appreciated. ------------------------------ Joe Hargrave ------------------------------39Views0likes1CommentRe: Upcoming Changes to JavaScript in Quickbase
@Evan Martinez Thank you for the answer; but as you already know, it's a non-answer. I do understand that it's the only answer you have, and I'm not pointing fingers at you, personally. Can you please verify for me which of the cutoff dates applies to iframes on forms? Even my QSP doesn't understand which date applies to those. My bottom line is simple, and it seems a lot of folks will be in the same boat, though they may not be wording it as strongly. If I cannot continue adding these elements specifically to forms, I have to abandon Quickbase. Period. This HAS to be allowed in another manner, BEFORE the cutoff date, so there is no downtime on existing functionality or on adding new iframes within forms. If there is any downtime on that ability, then I am no longer a QB customer. There is no other alternative for me, and I won't / can't even consider such. Adding the functionality to code pages accomplishes nothing for me at all. These iframe inserts have to remain ON FORMS. I have also put in a request through the help system, and my QSP is looking for answers. Due to the fact that I have all documentation from time of sale, including a recording of a tech call/screen share where I was shown this functionality to secure the sale, if this function goes down, I will be looking for two years of full refund, as well as any cost for QSP development, from QB. I won't elaborate any further on a public forum, but I'll make as big a deal of this as a little company from Texas can make, and from reading all the community posts and commentary here, I don't think I'll be the only one. QB needs to really consider their customers here, and they need to consider what is the right move for their business in a world where public reviews and comments can make or break even a large company's business and public reputation. I just need answers. And I don't need to have to wait until even closer to the deadline. If this functionality won't exist soon, I need to start app development on a competing platform YESTERDAY. Even if iframes had to be submitted and approved, and the workflow was slowed... I don't understand the "security issue" and I don't care to. It's not an issue that affects me or my company's app, so it's not relevant to me. I don't need to understand the tech side of it. I need to know what the solution is, or will be. And I need to be ensured that the new method will be released before the old method is shut down. Keep in mind that you're shutting down features your own team has designed for many of our apps. Saying it was technically never 'supported' isn't going to fly with your customers, nor will it fly in other venues due to precedent set by your own employees and QSP's. Please do everything in your power to alert the powers that be to the fact that it's imperative they not close features without replacing them, breaking the apps many of us rely on to run our businesses. We placed a massive amount of faith in QB when we chose to hang the success of our businesses on your software, and your promises. This company is my only way to support my family, and over 100 other employees. This app IS the way we run our business. This isn't play time. These aren't video games. This is our livelihood y'all are screwing with, and yes... that one feature makes or breaks the entire product for my company's use. And I don't seem to be the only one. Y'all are the 'big guy' here. Treat your customers right. Do the right thing. Don't make this blow up. Please.1View0likes0CommentsRe: Upcoming Changes to JavaScript in Quickbase
@Evan Martinez could you please clarify something for me/us? I've read the entire thread and I'm still confused. Here's the bottom line: I use forms that have embedded iframes containing small web pages of information that are built on our secure website. Additionally, I embed videos from Vimeo and PDF's into forms. This is all core functionality that I knew I needed, and investigated thoroughly with my sales rep from QB two years ago, before spending hundreds of hours developing our app on your platform. At that time, in order to close the sale and get my business, the examples shown to me by your own internal team, were examples straight from the MagicButtons app that I utilized. If they weren't technically 'supported even back then (as indicated in another thread), then why did your sales team use those features when they needed to show that functionality to close the sale? More importantly: I'm not even complaining about having to rework all this. I should be, but I'm not. What I need a simple answer to is this: Is there going to be a new way that I can learn, to embed outside web pages, PDF's and videos INTO FORMS specifically? The bottom line for me is that I've spent time that can't be regained, thousands in outside developer (your partners) help, and about 40k in subscription costs with Quickbase. As a small business doing only 3 million a year in revenue, that's a lot of investment. If there is a way to continue putting data from our website (pages designed for that purpose), videos and pdf's into forms, then I'll bite the bullet, learn the technique, and invest the time into getting it done. Sucks, but I'll do it. However, I'm not seeing where code pages would fix this. If I can't continue creating forms with these outside elements (embedded pages, videos and pdf's), then my ability to meet my needs through use of Quickbase comes to a close in August of 2021. And I've wasted an immense amount of time and money. What I would do as a recourse is something I'll have to figure out. But I need to know as soon as possible.... will I be able to continue doing the very thing that caused me to purchase Quickbase as a platform? Or not? The sooner I can get this answer, the sooner I can start figuring out what actions to take, what other solutions to explore, etc.1View0likes0CommentsRe: Form Appearance on Mobile
Hey Mark, So I found the solution for this, just FYI. And I found it by googling different terms, which led me to a similar question that YOU actually answered a year or so ago. LOL. Either I didn't explain myself well enough, or this simple solution didn't occur to you, but here's the solution I got from your previous post, and it works perfectly for my application. For each of the five new forms I'm using within Clientpoint's browser (our client portal solution where we embed lots of things, some of which come from Quickbase) - I simply add &fullver=1 to the end of the URL, and it forces the full version for that URL, which solves my issue perfectly! Just thought I'd report back that I found the answer..... from the 'ghost-of Mark-past'. ------------------------------ Joe Hargrave ------------------------------95Views2likes0Comments