ContributionsMost RecentMost LikesSolutionsRe: Search Widget to render results - not load recordThis function would be VERY helpful if there was an option to display 1 result in the report view rather than loading the form. ------------------------------ Justin Ferris ------------------------------ Get Base64 of FileIs there any was to encode a file attachment field into base64 in QB? ------------------------------ Justin Ferris ------------------------------ Automated Redirect to a FormWe are trying to build a method by which a user can click the edit button on any record in a certain table and be redirected to a form that is set by a formula. So far we have built in the default form for that table an iframe which links to a code page in which there is javascript that opens a link to the form that is set by the formula field in a new tab and closes the previous tab. Unfortunately once the user gets to the form and tries to save the form, it gets stuck on the saving screen. Any idea what is causing it to get stuck on the save screen? ------------------------------ Justin Ferris ------------------------------Routing User to Different Form Based on Field ValueHello, I have a process where users view a case file and work the file. We have grown so now we have several different types of case file and need to use a different form for each file type. I can imagine several ways to do this, but none are clean. Below is a list of what we tried. We tried using an iframe that linked to a formula url field, this worked except is displays the QB header twice and limits the screen size (iframes are apparently not responsive in QB). We tried using one "mega-form" with conditionals, but we hit the embedded report limit and certain fields need to be on multiple forms which QB disallows. We tried creating a different table for each file type but that breaks QB search widget (search widget can only search 1 table at a time). The best solution we found was to create a rich text field that displayed a link to the various case type forms, but then we lose the functionality of the edit and view buttons that display on every report and the search widget. Are there any other solutions to this issue? Edit: The real issue seems to be QB does not support building code at the routing stage of the application. Is this common web application functionality being considered for a future update? ------------------------------ Justin Ferris ------------------------------