EricEvans_Varga
Qrew Cadet
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: The legacy exchange will be replaced on March 24th, 2024
While the new Exchange is great to be able to quickly find and implement enhanced native QB elements, I feel the Legacy App Exchange provided an invaluable resource of ideas and non-native QB enhancements. It was a great place to seek peer-to-peer solutions for common (and some uncommon) problems. Even with a full library that may have seemed cluttered, I was able to find at least one to two apps that were useful, whenever I searched for something specific. I sincerely hope there is a plan to make all of the apps that were behind the Legacy App Exchange wall available to Quickbase Builders in some sort of format.Uploading to File Attachment Field - Error Received
Anyone else experiencing issues uploading docs to a file attachment field? It started for us today (May 26, 2023) around 11:00 AM Central. I've tried multiple apps in our realm plus multiple apps on a separate Builder Account realm, and no success. We all just keep getting this error message when attempting to upload anything: I wasn't even able to open a Support Case with QB, I just kept receiving error messages. I tried with and without attachments in the Support Case and just kept receiving the same error message. ------------------------------ Eric Evans Vargas ------------------------------Table report not visible in some roles when CSV output is selected
We have a table report where the output format selected is Comma Separated Values. The report shows in the reports panel for the Administrator role, but is completely hidden for users in other roles. What in the role permissions could possibly restrict CSV reports from being visible in certain roles? We've double checked: All roles have access to the report - it is visible when output set to "Normal" Role normally does not have access to Import/Export, but we removed that restriction while testing and the report still was not visible when set to CSV Save Common Reports is also normally off for the roles, but we removed that restriction while testing and the report was still not visible when set to CSV We rebuilt the report and it is still only visible when the output is set to "Normal" Hide UI for creating and customizing reports option is not selected The report will export as a CSV when accessed by a button on a Homepage, so the report is available, it just won't show in the panel. Any thoughts? ------------------------------ Eric Evans Vargas ------------------------------Dashboard Reports - Formula-Rich Text fields as URL Buttons
Has anyone else run into issues getting Formula-Rich Text fields (as buttons) to run a process when clicked? Formula-URL buttons work as designed, but when I try to consolidate multiple buttons into a Formula-Rich Text field to conserve precious real estate on a Dashboard, clicking the button returns an error The buttons add a child record and redirect to where the button was clicked. They work as designed when they are clicked from a Home Page or a report, it's only on the Dashboards where these fail. ------------------------------ Eric Evans Vargas ------------------------------Button to Create Child Record, pass data through to a Code Page and require additional data entry on that Code Page
There are probably easier ways to do this, but I am looking for a way to create a child record on a parent, pass some values to the child and have users add data into two fields using a code page. For ease of use, we do not want Users to interact with the child records, other than the fields they are entering data into when the record is created (why we're using a code page). Currently, I am able to create a code page that will Add a record to a table with as many field updates as I want, but I am unable to relate this record to a parent. Additionally, I am able to create a child record, pass certain values to the child and redirect the user to a code page for data entry into one field. That Button lives on the parent record, and the code page opens a field for users to enter a value for a field (see line 9 of the screenshot below, that is the field where the data entry is dropped into): borrowed code page from the Magic Buttons application Now if only I could do the combination of these. Anyone have any ideas? I've researched the Code Pages Sample App, but all I can find in there is how to create and edit a record using a code page. I did not find anything around creating a child record. ------------------------------ Eric Evans Vargas ------------------------------Extract Time Zone from [Date Created] to use in other formulas
I am trying to extract the time zone from the [Date Created] field, unsuccessfully. I have tried creating a Formula-Date/Time field to include the Time Zone, then creating a Formula-Text field to turn this field to text, but I still get the same result; the [Date Created] as a text field not including the time zone. What I am trying to do is create a formula downstream that will convert the date created to a new field that is targeted to the Users location and time zone. I already have the work done to be able to manage time zone differences and can piece together a formula-text field that will display the current user's time zone with date created, but I am now trying to account for Daylight Saving Time. Basically, what I'm trying to have QB do is: If the time zone in [Date Created] is "CDT" then calculate time difference based on Daylight Saving Time, otherwise calculate time difference based on Standard Time. I can get around this by adding to the formula some conditions to look at date ranges (based on when DST is active), but I'd really prefer not to. Thanks for any insight into this idea. ------------------------------ Thanks! Eric Evans Vargas ------------------------------Re: Upcoming Changes to JavaScript in Quickbase
While I can see this as necessary, it will be devastating to those of us who are neither software engineers nor experienced in Java, but instead are community users and builders who rely on the low-code capabilities of Quickbase. Many of us utilize these fields and borrow by copying and pasting from other sources and adjusting to fit the needs of our applications. We have numerous applications (hundreds) in our organization where we have utilized java script in buttons to consolidate manual processes and steps and to simplify the lives and the work of so many of our end users. While they seem so simple, so many of these buttons that we've created (combined with Actions, Webhooks, and Automations) have even knocked legacy systems out of contention when it has come down to replacing applications we have built with full-purpose programs. Simply due to the power behind a user clicking one button to generate multiple activities and saving time and energy by completing various tasks and steps that would otherwise have to be done manually. I sincerely hope that Quickbase is looking at a way to natively allow users who are not familiar enough with java script and code pages to continue to utilize the low-code power of Quickbase to its fullest extent. I apologize for the commentary and not necessarily adding any valued solutions or ideas to the comments section, but I felt the need to air what a huge blow this will be to many of us who are end-users turned app builders.
