JoeHargrave
Qrew Trainee
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Quickbase Native File Attachment Question
Absolutely Ember, not a problem. For the record though, Mark answered this and generally speaking, I'd trust his answer over mine. :) Below is the code for the button I got to work. This is basically a download only button, set to show in 'view' mode only, so our clients can easily download their documentation. It's downloading the document attached to the specific file attachment field id number. My button has some styling parameters in it as well, which can be changed or ignored. In this case, the field id number for the attachment field (where we attach the document internally) is 367. Additionally, it was important to me that the button NOT show up at all if there is nothing attached. We have several of these fields, but not every customer has every attachment that is relevant to them. This one is for a base contract, and the button simply says "Download Your Contract". If( [Contract - File Attachment] <> "", "<a \n class='Vibrant' \n href='" & URLRoot() & "up/" & Dbid() & "/a/r" & [Record ID#] & "/e367/v0' \n target='_blank' \n style='\n display: block;\n width: 100%;\n text-align: center;\n border: 1px solid black;\n border-radius: 24px;\n color: #000000;\n background: #a3ccc8;\n padding: 10px 16px;\n text-decoration: none;\n font-family: sans-serif;\n '>\n Download Your Contract\n </a>" )20Views0likes0CommentsQuickbase Native File Attachment Question
I think this is a simple thing, but I've been struggling with it for a while, so I thought I'd ask the community. I have a direct quickbase file attachment on a form. I want to only show that in edit mode (easy), then I want a button that will download that file when in view mode. I've tried formula URL and Formula Rich Text, but I can't get the syntax right I guess, because I continually get a 400 error. Can someone tell me how to accomplish this please?109Views0likes4CommentsLimit 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 ------------------------------128Views0likes1CommentTask 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 ------------------------------68Views0likes3CommentsRe: 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 ------------------------------64Views0likes0CommentsNew 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 ------------------------------49Views0likes2CommentsFormat 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 ------------------------------52Views0likes1CommentRe: 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.1View0likes0Comments