ContributionsMost RecentMost LikesSolutionsRe: Application variablesThank you Mark! We use Application Variables in an app for running & tracking special projects. There are three sub-dashboards with dedicated reports to track a project, and the project name is in a field within the records for a project. That project name field is also set to an Application Variable, when they match a project's records will show on its dedicated project dashboard (1, 2 or 3) For example: Application Variable | Data Field for a project [SpecialProjectFlex1]=[Project] I used a report level Logical / Checkbox formula field to make this test. When this is true, the records will display. With your suggestion above I was able to make a simple report on the main dashboard to show what the active projects are and which dashboard they use. I made a report in the main table to show only record #1. (I had to show at least one record for the report to work. There is nothing within record #1 that was needed.) I made a report formula Text field to show the contents of the three Application Variables with plain text to say which dashboard each is associated with: In the report I only show that formula field. (Again, nothing from record #1 matters for this to work.) I added that report on the top of the main dashboard next to the buttons for the three project specific dashboards. It looks like this: Now anyone can tell at a glance which dedicated dashboard they need for the project they are assigned to. Thanks for the idea! - David in Tucson Re: Can somebody help me create a report for loan/payment balances and a report to track past due payments?Link tested & verified 4/26/19/djlRe: Can somebody help me create a report for loan/payment balances and a report to track past due payments?Verified link to example Quick Base app 12/18/18/djl Re: Created a Copy of an Existing App and Want to Use Existing Fields to Link to a New Related TableHi Esther, There is a pair of apps that have been working for years. One part of the pair is the work being done. The other part of the pair is the details about who does the work. There is a relationship between the two so that people doing the work can select their name from a drop-down list to indicate that they did the work -- thus letting managers run reports on productivity. Due to a business change the team members will be splitting to wind up in two completely different businesses. I want to maintain the functionality for all concerned, however must split the people into two different who-does-the work tables. Since productivity reports are linked to who did what, once I make this new relationship, I'll essentially have the same person showing up as two people -- one from the old team, one from the new team. I was looking for a way to preserve continuity of reporting while making the split and through the conversation above with Matthew and Mark, realized that this logically canot happen. Even if I could change the pointers as I was hoping to, it would break the historical records -- since it really is two different who-does-the-work tables, there is not a way to use one field to point to both of them. So, I've chosen to keep the existing set-up until the end of the next fiscal reporting period; and then make the change. This will at least make reporting logical and the changes will not cause confusion. Thank you, DavidRe: Created a Copy of an Existing App and Want to Use Existing Fields to Link to a New Related TableHi Mark, Good to hear from you. I agree, that would be nice. This is a dictated business request. Imgine that these former teammates are going to be working for different companies and won't have access to the same data any longer. The specific data for the work each team does will stay with them. The link method I'm trying to preserve is to the table that lists all the team members, their managers, their desk-location, phone number etc. This person specific data is being split. Since the date of the work they did is associated with them I'd like to maintain that association while splitting out the actual people across two completely different teams. The key between the relationship is their Quick Base User ID, so that will remain the same. When I make a new relationship to the new (split off) team's worker app/table, I end up with Related-team-member-1 and Related-team-member-2. (1 links to the original app/table, 2 links to the new, split-off app/table). As I'm spelling it out in more detail it is clear that it just can't work. I'll go for the wait until the end of a reporting period approach. Thanks to you and Matthew for helping me process this! Thanks, DavidRe: Created a Copy of an Existing App and Want to Use Existing Fields to Link to a New Related TableThank you Matthew. The business requirement is that they be separated. The people will now be on completely different teams with different management. If I cannot find an elegant solution now, I can wait until the end of a fiscal quarter so that the reporting makes as much sense as possible. If anyone has an idea of an elegant solution to this, I would be eager to hear it. Thank you for your consideration! - David in TucsonCreated a Copy of an Existing App and Want to Use Existing Fields to Link to a New Related TableI have an app that I've been using for many years to contain common and frequenly used information about team members when assigning work. As team members do their work, they assign each record to themselves via a drop-down list that is a relationship to the team member table in this app. (They select Related-Team-Member.) Our team just had a split, and some will stay with the main team, and some will go to a new independent team. I made a copy of the app and have the team members split up so that they are listed in one of the two separate apps. The apps that they actually do the work from (the apps that link back to the main app) have historical data. To maintain continuity of reporting I would like to have the work app link to the new assignment app. If possible using the same "related" field. Ideally I would like to run reports in the do-the-work app so that the work done by team members (Bob, Mary, and Sumit, for example) would seamlessly show work they did in the past and work they do in the future. Is there a way to create a relationship to the new assign-the-work app in the existing do-the-work app and have it use the same Related-Team-Member field in the do-the-work app to access the related record in the assign-work app? Thank you in advance for your assistance. - DavidRe: Form(s) on Home PageHi Meredith, I needed somthing like this for customers to fill out a form and submit it to our Quick Base. I used a "pages" Code Page to make a stand alone HTML page with a standard HTML Input form. w3schools.com is a great resource for the details of the HTML page. This may be a bit of a learning curve, and it is worth it! The web page is submitted to Quick Base as an API call. In summary, these are the key elements. 1) Start the HTML form: Tutorial here: https://www.w3schools.com/tags/att_input_type.asp <!-- Standard QuickBase form Header. Update the Token ID as needed. --> <form name=qdbform method=POST onsubmit='return validateForm(this)' encType='multipart/form-data' action=https://intuitcorp.quickbase.com/db/your-db-id-here?act=API_AddRecord&apptoken=your-token-here> <input type=hidden name=fform value=1> 2) Ask for the fields you want to input (I used a table for formatting, which may be old-fashioned these days -- but it works.): <table cellpadding=0 cellspacing=0 border=1> <tr> <!-- Set up the Yes / No response area --> <td bgcolor="#F4F4EA" style="text-align:center;"> Yes </td> <td bgcolor="#F4F4EA" style="text-align:center;"> No </td> </tr> <tr> <!-- The Answer Buttons. Set the desired Field ID. This is a Yes/No question. --> <td bgcolor="#F4F4FA" style="text-align:center;"><input type='radio' name= _fid_9 id= _fid_9 value="Yes" /></td> <td bgcolor="#F4F4FA" style="text-align:center;"><input type='radio' name= _fid_9 id= _fid_9 value="No" /></td> </tr> </table> _fid_9 is the Quick Base Field ID I want this specific data to be placed in. You can get the Field ID numbers from the Fields list in Quick Base. 3) End the HTML form with the SUBMIT button: <!-- * --> <!-- Quietly pass the fact that this is the OM Save VOC. --> <!-- * --> <input type="hidden" name= _fid_13 id= _fid_13 value="OM Save VOC."> <!-- * --> <!-- You can Pass a piece of standard information to the Quick Base record with This Method--> <!-- * --> <input type="hidden" name= _fid_11 id= _fid_11 value="The Text You Want to Send in Quotes> <!-- * --> <!-- Pass the URL for the Thank You page (which is another Quick Base Code Page) --> <!-- Used the HTML form's "rdr" for Redirect URL option --> <!-- * --> <input type=hidden name=rdr value='https://intuitcorp.quickbase.com/db/your-dbid-ID-here?a=dbpage&pageID=the-page-ID-Number-of-your-Thank-You-Page-Here'>; <!-- * --> <!-- Center the Submit button on the page. --> <!-- * --> <table width = 100%> <tr> <td> </td> <td> <input type=submit value="Submit Survey"> </td> <td> </td> </tr> </table> </form> The page was set as the dashboard for the customer role (in my case "everyone on the internet".) It was the only thing they could do for security. If your audience is internal and you can just give them a link and have them bookmark it. Then anytime they want to come and submit a form they just go to the page directly. I trust this is useful. - DavidRe: Is it possible to share a quick base view with nonQbase users (read only) via GetResultstablesHi Rocketc, If you have the ability to create a role with read-only/view access for Everyone on the Internet (this may be limited by your domain administrators), then create the report, set the fields to be visible (recommend read-only) to your Everyone on the Internet role, then you should be able to do it. You'll need to set up the application Token and other security for the API to access your app. I've done this for some customer facing applications. David_in_TucsonRe: Converting a QB entered/formatted Phone number to a 10-digit numberThank you Mark.