Forum Discussion
Clicking the edit button will always take the User to the default form based upon their Role in the application.
You can build a custom button that will take the User to any form that you want to direct them to. The logic about that can be as complex or as simple as you want.
This variable defines a URL that will put the User on to the current record, in Edit Mode using form XX.
var text URLEdit =
URLRoot() & "db/" & Dbid() & "?a=er&rid=" &URLEncode([Record ID#]) &
"&dfid=XX"&
"&z=" & Rurl();
- awood2 months agoQrew Member
I have a URL field for each form with the formula:
URLRoot()&"db/"&Dbid()&"?a=dr&rid="&ToText([2025 Record ID])&"&dfid=11"
That brings them to the form with form ID 11, but when they hit edit it goes back to the role-based form.
When you say "build a button" is this a field I can add to a report (vs an element added to a form)? That's where the current links are, so that's where I would like the user to go to access either form.
- MikeTamoush2 months agoQrew Commander
It's always bugged me that if you use the native edit button, it edits on the default form, rather than the form the user is currently on. The work around, as you found in this thread is a custom edit button.
I haven't tested on new forms, maybe new forms will launch into edit mode based on the current form being viewed?