ContributionsMost RecentMost LikesSolutionsRe: Upcoming Changes to JavaScript in Quickbase@Evan Martinez - Some of the use cases of JS in our formula fields: 1. Popup a small window to display a report from an existing form to provide additional details. For example in our Pricing tool, a small icon shows projects of similar type and size listed by the contracted price in a new popup, which is extremely useful. It would be clunky to do the native way of opening that report and navigating back 2. In order to keep the focus of the user and provide better UI, we have several buttons that perform a certain action. But the button color is grey which changes to a bright green or a blue when hovered over. 3. Third use is is a simple JS confirmation prior to perfoming an action like archiving/deleting to ensure that the click on that icon/button was intentional. We use an inline formula to compare the response and then make that API cal using a custom URL plus redirect. Other examples pertain to one or more functions built via codepages within a record form for performing a particular activitiy. For example users can open a dialog to upload multiple files to a BOX folder with the metadata that is associated with the record where this image onload technique sit on.Re: Upcoming Changes to JavaScript in QuickbaseMy organization along with several others heavily uses JavaScript across the application to perform a multitude of tasks, like iframing, hover over css change, save and redirect, confirmation dialogs before actions etc. If you are really a customer centric company, you would provide an alternative/easy way to accomplish those common use cases before just disabling things and breaking applications that have evolved over years to truly meet the business needs. Disappointed that the transition plan you have is not good enough.