Saving record glitch
Hello,
When the user clicks the table button to add a new record and then saved the record the screen will go back to the previously entered record instead of displaying the current entered and sa...
Forum Discussion
Commenting on this again as I haven't found a solution to this issue
------------------------------
LB
------------------------------
I tried and every time it lands on the newly created record. I can't get it to fail in the way you are describing. Does this happen with every table, or only a specific one? This may be something for customer support to look at.
------------------------------
Mike Tamoush
------------------------------
- Mike and LB, are you both using the new form-builder? I've had similar frustrations with the new form-builder if the buttons are no-plain vanilla formula-URL fields displayed as buttons with "&z=" & Rurl() at the end of the URL formula.Or to put it differently, the combination of new-style forms and rich-text buttons can be treacherous. Sometimes it help in to append "&aftersaveview-1" to a rich-text add-button that's on a new style form. That forces the original record to re-display in view mode after adding, say, a child or parent of that record.Alex
Ahh good call. I am using the old form, so perhaps that is it. But your response led me to another question you may have an answer to:
If I am on a child record, as long as I launched from a report I will have the next/previous/return option on the top right.
However, if I have a custom button to run something (in my case, i have a custom save an next button I made), it obviously removes those.
You mentioned the &aftersaveview-1 for a new style form - do you know any tricks to adding on to an old style form custom button, that preserves the current next/previous tags?
------------------------------
Mike Tamoush
------------------------------Apologies. I had some typos in my previous reply. Mainly a dash instead of an equals. So &aftersaveview=1 is the correct addition to force view-mode on a record created from a rich-text button within a new-style form.
Regarding Mike's follow-up, sorry I don't have any insight on that scenario. But possibly using &aftersaveurl=" <your target url> would be worth trying. It exists as an undocumented feature on the new form-builder, but I haven't tried it.
Alex
------------------------------
API Administrator
------------------------------
