afterRecordInsert Server-Side Event -- Can't emit to browser??

[mikeallenbrown]

Is it not possible to emit JS to the browser from the 'afterRecordInsert' event?

I was going to use this event for some new records handling.


ScreenShot_005.jpg


ScreenShot_006.jpg

[Davidk]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

I don't think you do it there. afterDialogValidate can reference rtc.flagRecordWasSaved so that you can return Javascript based on that. Have a look at the notes for afterDialogValidate.

You also have Client-side Events... After save succeeded Javascript.

[mikeallenbrown]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

I don't think you do it there. afterDialogValidate can reference rtc.flagRecordWasSaved so that you can return Javascript based on that. Have a look at the notes for afterDialogValidate.

You also have Client-side Events... After save succeeded Javascript.

Thank you, David. I'll take a look. The handling I need would be for new records only. Not sure how I'd detect a new record client-side in the After save succeeded event.

[Davidk]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

Ok then... instead... use the Client-side Event "After save" AND "Data to pass to client side event". The "e" object gets passed into your client-side function... and you can load up the "e" object with server-side data. E.g.

After save function: myAfterSave
Data to pass: __saveType = rtc.primaryTableEditMode

and the Javascript function would be...

function myAfterSave(e){

	debugger;
	var saveType = e.__saveType;

}

where saveType will be "Enter" for an Insert and "Update" for... well... an Update.

[mikeallenbrown]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

Oh this is great! Thanks David. This is exactly the type of thing I was looking for.

[GGandhi]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

Thank you, David. I'll take a look. The handling I need would be for new records only. Not sure how I'd detect a new record client-side in the After save succeeded event.

will you be using same ux/dialog to insert as well as update? not the usual method as far as i know.
you will have one ux to insert the data so when that saves it is the new record, is that not correct? or a new functionality is present in version 12 where you can mix those insertion and update on the same ux?

edit: the example you posted in the first post is expecting a variable not a string, that is why it does not work.
sorry, noticed you used e.javascript, that should have worked.

[mikeallenbrown]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

This particular UX inserts and updates records.

[GGandhi]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

if you add this code right after the save data action script you will see whether is update or insert

if rtc.flagRecordWasSaved then
        dim v as c
	v = rtc.primaryTableEditMode
end if
e.javascript = "alert('"+ v +"');"

then you can use the variable v for something else

edit:
https://www.screencast.com/t/y5OmIGmXxvxH

[mikeallenbrown]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

Nice. Thanks Gandhi!

[Davidk]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

But... e.javascript is not available in that server-side event function.

will you be using same ux/dialog to insert as well as update? not the usual method as far as i know.

Not sure I understand... why not? Why would you have 2 Components when 1 will look after Inserts and Updates?

Agreed... moving rtc.primaryTableEditMode into afterDialogValidate is much cleaner.

You also need to take care of the e.javascript that's already been created... and look after your variable in any case...

dim v as c = ""
if rtc.flagRecordWasSaved then
	v = rtc.primaryTableEditMode
end if
e.javascript = e.javascript + "alert('"+ v +"');"

[GGandhi]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

Not sure I understand... why not? Why would you have 2 Components when 1 will look after Inserts and Updates?

take a look at my video david, once i realized that mike is just adding another button to do both insert and update, my head became clearer.
old age has its problems.

about 2 components-
i am not in the habit of trusting the users to be diligent in entering the data, give them a chance they will play with your data. if you have one dialog for insert and update, it will show all fields including primary key and the user can enter the primary key and without hitting the button enter new information and they will submit the data. may be you can try in your system and see what happens. even if you were to succeed preventing unauthorized entry of new data, you will find it hard to convince me.
my idea is
for update i will have the primary key and no other field shown unless they hit the button, so only that record will come out.
for insert i won't have the primary id field, it will be hidden. so they cannot enter but auto increment nature will insert the next id.
well that is my thinking. you are an expert you know better way to do i am sure.

as far as e.javascript
you are correct, it is better to append the original one.

edit:

and look after your variable in any case...

i think you are referring to dim v as c = "" assigning default value. while that is a perfect use, in alpha it is not necessary, as far as i know.
simple v = "gandhi" will dim a variable v to a character type and assign empty space and then assign value "gandhi" to that variable.
dimming and also assigning value is necessary if that variable is going to be used globally or in functions where that value needs to be reset to evaluate to proper value.
dimming to a character value in that declaration is all that necessary, again as far as i know.

alpha, being an elephant, a very intelligent animal on the planet, knows how to take care of us, i am sure.

[Davidk]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

This is from the notes in afterDialogValidate...

In addition, since the Server-side Action will have already set the value of the e.javascript variable, you will want to append your code to e.javascript

If you don't do this, then the javascript set up by the server-side action will not get run.

i think you are referring to dim v as c = "" assigning default value. while that is a perfect use, in alpha it is not necessary, as far as i know

It's not a question of how you create your variable... but rather that if you don't create a variable outside your "if" statement... and the code inside your "if" statement does not run... then the code after your "if" statement, which uses the variable, will fail.

[GGandhi]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

if the variable is created outside and the if statement fails the variable will be created but will not used just gets thrown away, but if statement succeeds then if the variable is needed and it gets created and used. certain part of the memory is not used.
is that not right?

[GGandhi]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

This is from the notes in afterDialogValidate...

In addition, since the Server-side Action will have already set the value of the e.javascript variable, you will want to append your code to e.javascript
If you don't do this, then the javascript set up by the server-side action will not get run.

i have said, you are correct, you don't need to reiterate.

[Davidk]

Re: afterRecordInsert Server-Side Event -- Can't emit to browser??

if the variable is created outside and the if statement fails the variable will be created but will not used just gets thrown away, but if statement succeeds then if the variable is needed and it gets created and used. certain part of the memory is not used.
is that not right?

I'm confused now. All I was pointing out is that your code, the following code, would blow up if the code inside the "if" statement did not run...

if rtc.flagRecordWasSaved then
        dim v as c
	v = rtc.primaryTableEditMode
end if
e.javascript = "alert('"+ v +"');"

Just make sure you create your var outside the "if" statement and you'll be ok.