Function was not recognized

[Steve Workings]

Can't seem to get past this one. I have a javascript function that includes this:

{grid.Object}.ajaxCallback('G','{Grid.RowNumber}:all','xbServerIsAvailable','',ele,{deviceOfflineFunction: function() {   }});

and an Xbasic function:

function xbServerIsAvailable as c (e as p)
. . .
end function

Yet when I call the javascript function, I get an error alert:

Fatal error executing Ajax callback: Function:
'xbServerIsAvailable' was not recognized

I've re-named the function in several ways to make sure it's not anything reserved. I've simplified it to just three lines to return a simple alert in case there's something amiss with my Xbasic code. After about 2 hours I'm outta ideas.

Any thoughts?

Update 2.5 hrs later - this is really annoying. I'm making the callback directly from the button - skipping any intermediate javascript, and same problem. The button for my testing just does this (yes, I'm trying different names for the function)

{grid.Object}.ajaxCallback('G','{Grid.RowNumber}:all','xbServer_IsAvailable','','',{deviceOfflineFunction: function() {   }});

I've re-started the A5 server as well. No joy.

[mumfie]

Re: Function was not recognized

Can't seem to get past this one. I have a javascript function that includes this:

{grid.Object}.ajaxCallback('G','{Grid.RowNumber}:all','xbServerIsAvailable','',ele,{deviceOfflineFunction: function() {   }});

and an Xbasic function:

function xbServerIsAvailable as c (e as p)
. . .
end function

Yet when I call the javascript function, I get an error alert:



I've re-named the function in several ways to make sure it's not anything reserved. I've simplified it to just three lines to return a simple alert in case there's something amiss with my Xbasic code. After about 2 hours I'm outta ideas.

Any thoughts?

Update 2.5 hrs later - this is really annoying. I'm making the callback directly from the button - skipping any intermediate javascript, and same problem. The button for my testing just does this (yes, I'm trying different names for the function)

{grid.Object}.ajaxCallback('G','{Grid.RowNumber}:all','xbServer_IsAvailable','','',{deviceOfflineFunction: function() {   }});

I've re-started the A5 server as well. No joy.

Hi Steve,
Luckily I have not seen that error recently.

A couple of things to check
Is the function defined in the UX/grid or in an AEX ? Can try move to alternative
Does the xbasic function xbServerIsAvailable return a result?
Does the component generate any javascript errors?
create a temporary button and recreate the ajax callback to see if that works
shorten the function name and check if encrypted

[Steve Workings]

Re: Function was not recognized

Is the function defined in the UX/grid or in an AEX ? Can try move to alternative
This and all other functions are in the UX and work fine. Don't have an AEX so haven't tried that. I have a dozen Xbasic functions in this UX that all work just fine.

Does the xbasic function xbServerIsAvailable return a result?
I've simplified to just return "alert('callback');" and both Selwyn and I get that result in Working Preview

Does the component generate any javascript errors?
Nope.

create a temporary button and recreate the ajax callback to see if that works
Have tried that.

shorten the function name and check if encrypted
It's not encrypted, and have tried all kinds of different names but not focused. Just tried renaming and calling it "xb" and same error.

[mumfie]

Re: Function was not recognized

Does the xbasic function xbServerIsAvailable return a result?
I've simplified to just return "alert('callback');" and both Selwyn and I get that result in Working Preview

So the simplified version works in Working preview but not Live preview/published. Not encountered that before ?
Is the function the only function in XBasic declarations or does it contain multiple functions.
If multiple you could try moving it to the top or temporarily remove other functions to see if that has any affect.

[Steve Workings]

Re: Function was not recognized

Correct. I've never seen this. I've now just tried this:

I added a new function:

function xb as c (e as p)
    xb = "alert('callback');"
end function

It's the first function in the Xbasic functions. I've completely commented out the second function, which is the one I'm trying to add. There are another 5 or 6 after that that work well. When I try a callback to the new XB function, I get the same error.

[mikeallenbrown]

Re: Function was not recognized

I tried this myself and your examples all worked in both live preview and when published. Are you running a pre-release by chance? I'm on 2689-4440. If you create a new component with just the XB function do you have the same problem?

My button calls this JS function:

function myFunction() {
	alert('JS callback works');
	//Call xbasic function now
	{grid.Object}.ajaxCallback('G','{Grid.RowNumber}:all','xbServerIsAvailable','','',{deviceOfflineFunction: function() {   }});
	return;
}

This is the Xb function:

function xbServerIsAvailable as c (e as p)

xbServerIsAvailable = "alert('XB callback works');"

end function

[Steve Workings]

Re: Function was not recognized

Yeah Mike I'm on pre-release 2716-4452 (and so is the server). But I've added other Xbasic and Javascript functions to this UX over the last few days. This is my very last addition, I was 15 minutes away from declaring this one done and being able to send a bill.

[mikeallenbrown]

Re: Function was not recognized

Pre-release 2752-4462 was just posted....maybe it'll be the cure for your problem.

[Steve Workings]

Re: Function was not recognized

With my current build I just created a new UX with one callback, one button to make the callback, put it on a page and published it. It works fine.

[mumfie]

Re: Function was not recognized

With my current build I just created a new UX with one callback, one button to make the callback, put it on a page and published it. It works fine.

Maybe duplicate the problematic component and remove features a few at a time and retest. It might start working again at some point and identify the cause.

[Steve Workings]

Re: Function was not recognized

I did try duplicating the component, that didn't do it.

I also tried putting the Xbasic function into a function library attached to the UX. Still no joy.

Edit: OK, I have now removed nearly everything. All that's left is the panelnavigator and cards - no content. All javascript, all other controls, all other Xbasic functions -- everything right down to this single button are gone. Still no success.

It seems I cannot add a callback to this component, but it's the parent UX for the application and all I need to do is add some functionality to it. Seems that I cannot, yet.

[mikeallenbrown]

Re: Function was not recognized

This may be a shot in the dark but at this point what else is there?? ...maybe copy/paste a few controls at a time from the problem component into a brand new component.

[Steve Workings]

Re: Function was not recognized

Mike - I was avoiding this. It has Geolocation stuff, a complete set of custom offline management functions, on and on. I'm worried I'll miss something. But, I just went ahead and did it and that appears to have done the trick. Further testing pending - gotta get a few other billable hours under my belt for today before I come back to this.

[TaiTai]

Re: Function was not recognized

Bump!

Interested on any progress with this topic. I have been working for 100+ hours on a UX which has been fine until last night, all with the candle burning .
My error occurs in PhoneGap only. Have commenced removing the new code I added to back track the problem. Will advise on / when I achieve success.

Question/Suspicion: Is there a limit on the actual size on Xbasic code you can add to a phonegap published app?

[TaiTai]

Re: Function was not recognized

Update! I fixed it. Did 4 hours of code rebuild without restarting UX from scratch.
I actually suspect that the version I had published was older than the version I was using in PhoneGap.
Why do i think this? Because I realised that my PhoneGap build was pointing to a ZebraHost server and not my local server.
I had not published the UX to this server.
I worked it out during my code rebuild as I moved some DB logic to a stored procedure.

On with the show!