ContributionsMost RecentMost LikesSolutionsRe: change the native add record button to go to a certain form instead of using the one this table is set to be used in view mode. Confirming this was a syntax issue. There is inconsistency in the way that the underscores are used in the field vs. the form identifier. Look out for the use of those underscores. Re: New Forms - Formula URL Button It looks like the issue is only in the preview of the form. Whether you preview from within the designer or from the list of forms in the table settings the buttons do not currently render. However, even if another form is still the default, if you create a new record, then append "&dfid=" then the ID of the form when you refresh, you'll see a live version of the form where the button renders as expected. ------------------------------ Tate Forgey ------------------------------ New Forms - Formula URL Button I apologize if I'm missing something obvious, but as I am trying out the new forms and added the stock add new child formula URL button, it is just text when I preview. Are buttons not rendering on the new forms? ------------------------------ Tate Forgey ------------------------------ Re: Duration field in Pipeline Outlook channelWell, it makes me feel a little better that this is on the fringes of even your vast knowledge. Thanks for the response. ------------------------------ Tate Forgey ------------------------------ Re: Duration field in Pipeline Outlook channelCoach, did you give this advice because of any limitations in Pipelines with duration fields? Can I use them in calculations like I would in a formula duration field? I'm trying to create a Pipeline to track how long a record stays in a certain status and part of that is trying to set up a calculation using duration fields and insert that value into a field in an Update Record step. However, it threw this error: Validation error: {'time_in_received_status': ["field 'time_in_received_status' could not be coerced", 'must be of integer type']} I could have other mistakes in what I'm doing, but I just want to make sure I can create duration calculations here or if I need to create fields in the form to do that. Thanks! ------------------------------ Tate Forgey ------------------------------ Abort Message Not Displaying in Mobile AppI couldn't find a reference to this. So, I want to make sure it is not just me. In the Quickbase iOS app the abort message does not display even though it is set properly in a dynamic form rule. There is an indication that something is processing, but you are returned to the form with no message. The abort action works in the sense that the record is not saved, but there is no message. I can get the "Display Message" action to display a message from another form rule I have. Also, testing in the same role I am logged into the app as there is no issue with the abort message displaying. Have people encountered this? I can create a banner that shows in the app with the same message, but it is weird. ------------------------------ Tate Forgey ------------------------------ Re: Calculate next 2nd Tuesday of a monthWhile I'm conceptualizing how to fix delta, I'm inserting a blunt force attack: Case(DayOfWeek( (FirstDayOfMonth(Today()))), 0, FirstDayOfMonth(Today()) + Days(9), 1, FirstDayOfMonth(Today()) + Days(8), 2, FirstDayOfMonth(Today()) + Days(7), 3, FirstDayOfMonth(Today()) + Days(13), 4, FirstDayOfMonth(Today()) + Days(12), 5, FirstDayOfMonth(Today()) + Days(11), 6, FirstDayOfMonth(Today()) + Days(10) ) ------------------------------ Tate Forgey ------------------------------ Re: Calculate next 2nd Tuesday of a monthThis is just what I need, Mark. Thanks! However, as I create the formula date field and look at it today (November 10, 2021) it produces an incorrect value. The date it produces is November 16, 2021. The second Tuesday of this month was November 9, 2021. The code should have given me the second Tuesday of next month (which it is calculating correctly). I'm trying to unpack your code, but if you get to it first, do you know why this is and how we can fix it? ------------------------------ Tate Forgey ------------------------------ Re: Removing Javascript Screen Refresh from URL Formula FieldsThere is a specific use of the previous JavaScript that doesn't seem to work with this new code. (Inspired by Coach!) I have a button on a table's form that redirects to a report on a different table with an "ask the user" filter and completes that filter with a value from the original record. It's part of a workflow to associate child records in bulk where the users usually search for an ID from the filtered list, associate the record with a formula button that also refreshes the page, and then search for another ID to associate. This has worked beautifully for years, and users loved it! I replaced the JavaScript with this code for the reload portion of the button and boom - busted. It seems like the report refuses to display with the filter as it did before. Instead of the reload, I think I'll need to create a redirect back to the same page, but reinsert the fields in the filter, which means I'll have to go hold them in a surrogate table just for this purpose (Coach's "User Focus" technique.) A bit of a pain, but I'm hoping that works. I must be getting crotchetier, but it seems all Quickbase's recent changes cause me a lot of work and bring me little benefit. Ugh. ------------------------------ Tate Forgey ------------------------------ Record with most recent date in one table for each record in another table with the same parent I've got a tricky request I'm hoping folks can help me with. I have a patients table. Related to that I have a patient tests table with test dates. There will be new data containing patient treatments that has a date and a type. I was naturally going to create a table for that and relate it to the patient table. The request is that for every separate test a patient has I identify the most recent treatment and calculate the number of days that occurred before the test. I had some "blunt force" ideas about how to get at this using summary fields on the patient, but I feel like there should be a more elegant way. Thanks! ------------------------------ Tate Forgey ------------------------------