I tried all possible settings, I cannot get back to the inserted record.
is seems to be very basic, but does not work for me.
I open a form in a new window (or as tab, same result) from a grid via the linked application after I click on add new record on the grid.
the form saves the record but stays in the insert mode or something.
options i tried:
navigation - Return After Inserting is On , (if Off the same result)
are there any settings or something that block normal way ?
This button says:
[TABLE=“class: nmTable nmTableStyled form_tab_id_blk_lnk_opn_desktop_navigate, cellpadding: 0, cellspacing: 0, width: 1914”]
[TR=“class: nmTrAttr nmTrHover”]
[TD=“class: nmLineV3”] [/TD]
[TD=“class: nmLineDesc”]Dont open a new blank record after an insert, instead go to edit mode.[/TD]
[/TR]
[/TABLE]
So it’s either a new blank form after insert of the same inserted form
Maybe you can make a custom button in which you combine the 2 functions below and hide the add&exit-buttons
add function: [SIZE=11px]onclick[/SIZE][SIZE=11px]="[/SIZE][SIZE=11px]nm_atualiza (‘incluir’);; return false;"[/SIZE]
close function: [SIZE=11px]onclick[/SIZE][SIZE=11px]="[/SIZE][SIZE=11px]document.F6.action=‘form_tblUitgevoerdeZendingen_1_fim.php’; document.F6.submit(); return false;; return false;[/SIZE][SIZE=11px]"[/SIZE]
If you succeed to make the button plz let us know how you did
regards
found it: simple
make JS button
from this button call JSmethods: A combination of the 2 line of code is not working. Only the first i executed. So You need to add a JSmethod for every JS function you have
JSmethod1();
JSmethod2();
JSmethod1:
[SIZE=11px]nm_atualiza (‘incluir’);; return false;[/SIZE]
JSmethod2:
[SIZE=11px]document.F6.action=‘form_tblUitgevoerdeZendingen_1 _fim.php’; document.F6.submit(); return false;; return false;[/SIZE]
the solution was easy but hard to find. actually , if you change toolbar , add a navigation, scriptcase is wel able to go to the inserted records by itself.
i already had issues with the toolbar, as it is buttons effect the form behaviour in unexpected ways, or you are not able to do some things programmatically because you miss some buttons.
but you do not not want to expose some buttons to the user. so it is very bad design to make such dependencies. i hope SC will improve it.
Buttons should be independent from the form properties and do not do weird things under the water.