ContributionsMost RecentMost LikesSolutionsRe: EOTI SAVE BUTTON Mark, thank you! A million times thank you. We are so busy this time of year that I am trying to cram in the coding update and this worked perfectly. ------------------------------ Rhonda Jones ------------------------------ Re: EOTI SAVE BUTTON I have tried to make it clearer using screenshots on the doc attached. ------------------------------ Rhonda Jones ------------------------------ Re: EOTI SAVE BUTTON Mark, No. So, they enter some basic info in the parent record and then click a Add Items button which takes them to the first record to enter in the child table. this button is the one Quickbase creates when you make the parent/child relationship link.It works perfectly. It creates the first child record and displays the correct Record Id, Order Number and Name. In this situation, the Record ID is the reference proxy and the Order Number and Name are lookup fields. It is here that my older users are having an issue. It is creating the second child record that is the problem. They can't figure out the drop down save button that is the native UI. ------------------------------ Rhonda Jones ------------------------------ EOTI SAVE BUTTON For the love of all things holy and before I throw my PC out the window.... I FINALLY got a button to add a new record to a child table with the prepopulated fields I need. Code is "<a href='" & URLRoot() & "db/btcpg7sph?a=API_GenAddRecordForm&dfid=2" & "&_fid_18=" & URLEncode([Related Request]) & "&_fid_20=" & URLEncode([Request - Order Number]) & "&_fid_19=" & URLEncode([Request - Name]) & "'>" & "<img src='https://expertclaimmanagement.quickbase.com/up/btegrvwjr/g/rb/eh/va/ADD%20NEXT%20ITEM.png' alt='Save & New'>" & "</a>" The problem is, of course, that it doesn't save the current form. So, I just set the application settings to auto-save if a page is navigated away from. The problem is that it still throws the Leave site warning message which confuses the 75-year-olds using this form. So I created this button var text url = URLRoot() & "db/" & Dbid() & "?a=er&rid=" & ToText([Record ID#]); var text link = "<a href='" & $url & "' data-replaceRid='true' style='font-size: 11pt;margin-left: 5px; margin-top: 0px; height: 33px; width: 160px; text-align:center;background-color:#13294d;color:white;background-image: linear-gradient(to bottom, #13294d 0%, #13294d 100%);' class='SaveBeforeNavigating Vibrant'>Save and Continue</a>"; $link but it doesn't actually save and continue, it saves and next. It repopulates a blank form and if I test it as EOTI, I get an Access Denied page. I realize the EASIEST way to control this functionality is the built in save button. Unfortunately, the lamen user hits Save and close every.single.time. Even with huge bold instructions explaining how it works. Because they do not have access to their records once they close it, they have to start all over or, what actually happens, is call me and I spend all day on the phone. I either need a way to have a save button that returns the EOTI to the page in edit mode (and I guess be told how to make sure the permissions are set correctly) so that they can then hit the add next item button or close button, or figure out a way to allow EOTI to access records with either the Order Number they enter which is unique, or the record ID number without them being able to see everyone else's entries. I know this is very jumbled. I'm 10 hours in and ready to dissolve my business at this point. It feels like I am being forced to use the native buttons even when they are the worst solution. I miss Java Script. I hate it but I NEED three separate buttons. One to save and continue, one to close and one to Add New. I have the close and add new figured out. ------------------------------ Rhonda Jones ------------------------------ Lookup field not populating when using custom Save & new button I have a child table that I needed to hide the native UI save button on. This is an EOTI app and unfortunately, EOTI seems to have a hard time following the simple direction of using the drop-down option on the save button to hit save and next if they need to enter more than one record. So I have to make "save and new" and "save and close" two large obvious buttons... I am using this code "<a href='" & URLRoot() & "db/btcpg7sph?a=API_GenAddRecordForm&dfid=2&_fid_19=" & [Request - Name] & "&_fid_20=" & [Request - Order Number] & "'>\n <img src='https://expertclaimmanagement.quickbase.com/up/btegrvwjr/g/rb/eh/va/ADD%20NEXT%20ITEM.png' alt='Save & New'>\n</a>" I have double checked the field names and numbers and when I hit my button, the URL syntax is correct, it shows the Name and the correct Order Number. It just isn't generating in the form and because that is the field that actually links the record to the parent table, nothing entered on the form is saved. Any help on what I am doing wrong? ------------------------------ Rhonda Jones ------------------------------ Filtering out duplicates on table reports I have a table report that shows all the claims that we closed for the month prior. Sometimes we have numerous claims that share a customer name and order number because the customer may have a large number of items or they may be different claim types. We already have fields that provide the totals across all the customer's claims that have matching order numbers and those are the fields the report is pulling in. As such, I need the report to leave off duplicate claims with matching order numbers and only provide the information for the claim with the earliest record ID. That way, each customer will show only once on the report so that the totals on the report are correct. Is this possible using a report formula or some filtering setup I am not seeing. Thanks so much! ------------------------------ Rhonda Jones ------------------------------ Re: XML Issue Perfect! Thanks a billion! ------------------------------ Rhonda Jones ------------------------------ Re: XML Issue I thought it was something to do with that! Thank you. Using that code, however, my button is gone (doesn't display) lol any thoughts ------------------------------ Rhonda Jones ------------------------------ XML Issue I am creating a button to change a status field. I am getting the XML style information issue. The button works correctly and I know it has something to do with the code not redirecting back to the rid but I'm not sure how to fix it. Here is the XML error This XML file does not appear to have any style information associated with it. The document tree is shown below. <qdbapi> <action>API_EditRecord</action> <errcode>0</errcode> <errtext>No error</errtext> <rid>8</rid> <num_fields_changed>0</num_fields_changed> <update_id>1679947786033</update_id> </qdbapi> Here is my code: (this may be overcomplicated. Probably an easier way to accomplish this) var text URL = URLRoot() & "db/bsy9zg874?a=API_EditRecord&rid=" & [Record ID#] & "&_fid_330=Review%20for%20Inspection&z=" & Rurl(); var text Image = "<img src='https://expertclaimmanagement.quickbase.com/up/bjvfbr5ux/g/rbh/eg/va/button_rev-for-insp.png'>"; "<a href='" & $URL & "' target='_blank'>" & ($Image) & "</a>" Can I get some help cleaning up this code to correct the error? thank you very much! ------------------------------ Rhonda Jones ------------------------------ Re: Corrected formula coding in Color-Coding Understood. That worked, thank you. That color page is also very helpful. ------------------------------ Rhonda Jones ------------------------------