Setting arbitrary message in transient message

[Pat Bremkamp]

I'm a rookie at JavaScript, so I need someone who is better to look at this.
I'd like to switch from alert messages to transient messages to let the user know what happened in Xbasic processing. This is a web application.
The processing can create a variety of error messages, so I was wondering, if there was an error, could I put the error message in a state variable, then display that in the transient message. Something like
In Xbasic
if pResult.error = .F.
RecentlyViewed = "{grid.object}.runAction('RecentlyViewedSuccess');"
else
e._state.MyErrMsg = pResult.message
RecentlyViewed = "{grid.object}.runAction('RecentlyViewedFailed');"
end if

Then in the JavaScript action 'RecentlyVIewedFailed'
var stateInfo = {grid.object).stateInfo;
var _MyErrMsg = stateInfo["MyErrMsg"]


var _html = '<div style="display:inline-block;">'_MyErrMsg'</div>';
var _options = {


Could this work?
Thanks,

[Pat Bremkamp]

Re: Setting arbitrary message in transient message

This is hopeful....
To get past the error checking, I has to change to var _html = '<div style="display:inline-block;">_MyErrMsg</div>';

and it displays the trainsient message "_MrErrMsg" in red. So I just need to get it to show the value of _MyErrMsg instead of the name.

Pat

[Davidk]

Re: Setting arbitrary message in transient message

Your _MyErrMsg is being treated as static text because it's inside the single quotes. Try...

var _html = '<div style="display:inline-block;">' + _MyErrMsg + '</div>';

[Pat Bremkamp]

Re: Setting arbitrary message in transient message

Thanks, David, that worked to put the text into the message, but I couldn't get the state variable to work, I'm giving up. What I'm trying to achieve is not worth all this trouble.

[Davidk]

Re: Setting arbitrary message in transient message

If you run your process twice you will find that the state variable is available the second time around. You're working with a Grid which is years behind in testing and compatibility with the rest of Alpha.

If you run the same process in a UX component, you'll find it works exactly the way you'd expect... the state variable is set at the server and is available in the client. Not so with a Grid component... Alpha at it's best... very little consistency. This kind of stuff waste such vast amounts of time for developers.

If you can live without running an Action, then you can accomplish what you want without involving a flakey state variable.

Instead, return a call to a Javascript function... and you can pass in your error message.

In your XBasic...

RecentlyViewed = "RecentlyViewedFailed('" + pResult.message + "');"

The Javascript function will be...

function RecentlyViewedFailed(MyErrMsg) {

	var _html = '<div style="display:inline-block;">' + MyErrMsg + '</div>';

}

This Javascript function will go into the Javascript Functions sections of your Grid.

[Pat Bremkamp]

Re: Setting arbitrary message in transient message

David, that's a great idea. The only reason for the state variable was to get the message into JavaScript. This is a much better way and much cleaner. Thanks.

[Pat Bremkamp]

Re: Setting arbitrary message in transient message

WooHoo! That worked beautifully! Looks like this...

Failed_Message.png

[RichCPT]

Re: Setting arbitrary message in transient message

If you run your process twice you will find that the state variable is available the second time around.

Sorry for jumping in on this solved issue, but I wanted to add my 2 cents:

I sent in an official bug report a couple years back about State variables not being initialized soon enough when rendering a Grid. The issue Pat found about a state variable not being available when expected is similar. I had to put a check in my code such that if the state variable was undefined then the code would not do anything. In my case the AA JS library would automatically call my code twice anyway. The second time around the state variable existed. Without the check for existence of the state variable the JS would get an error and not run any other JS for that event.

I like David's solution of returning all the JavaScript at once.