URLRoot() & "db/" & Dbid() & "?a=API_EditRecord&rid=" & [Record ID#] & "&_fid_6=Completed&rdr=" & URLEncode(URLRoot() & "db/" & Dbid() & "?a=q&qid=1")
For the formula above, if you have multiple pages where you want the button to appear, you can copy the field for each other page, like your dashboard, and each version of the formula would redirect to a different page. The setup for that is a little more complex but it provides the same streamlined workflow for your app's users.Then, if neither of those work well, that's when I would consider whether it's worth working with one of our partners to build a custom solution that may meet your needs better.
Hi Harrison, Yes, that's very helpful and detailed. Really appreciate the response.
To hear that iFrames will still be supported in the new form is a huge relief. I've also heard that, for old fields with JS, you will still be able to keep your JS. Is that true? If yes, it sounds like eventually, those will not be supported either, but that would come later. Is that accurate?