Interesting. I thought it might be something about the way the code was written. Historically, before I learned how to make this button to pop me into the other form, I had a report that was built to access that form - and if you click edit from that, you stay in the form you're in. I just assumed if you got into a form, the edit button would apply to that form, and it must've been something about how I coded the action in the formula URL.
We have used this approach, but it's not hugely successful because users end up on different forms when switching modes. Short of trying to replace all the default form buttons it seems there is no way to achieve the desired outcome. It would be really useful to be able to define simple logic to define which form to display.
Qrew Legend..... the alternative is to review your form and figure out how to use form rules to just have one form.
Yes, that should work in most cases. We found the logic required to deliver different UIs based on attributes of the record was becoming extremely complicated to implement and test. We also had to place fields on different tabs depending on these attributes, which meant the single form route wouldn't work (AFAIK :)).
Qrew LegendYa, you need to decide on the least worst option. Formula fields can be on the form in multiple places on Legacy forms. Not sure about New Style forms.
