Execption IWSession Not Processing Submit for TIWCGJQEdit

[MCarver]

CG Gurus,

A few versions back, I began getting the following error:

'The following exception occurred:
"myCGEditInner: The IW Session is not processing submit !"

These TIWCGJQEdit controls reside on a DialogEx, which resides on a CGFrame. The error occurs upon attempting to close the DialogEx, provided the data has been changed in a CGEdit. If no data for a CGEdit has been changed the DialogEx will close with out incident. Once the error surfaces, a subsequent attempt to close the DialogEx is successful and changes the data as expected. Note the "Inner" appended to the name of my control.

This error appeared to surface about the same time the zIndex behavior of the DialogEx was changed (probably coincidence). As a further point of interest, only a Databound CGEdit is affected with this error. And the data does not need to be changed to receive the error, but only receive focus.

Please advise, As I have been unable to find a resolution these last few weeks on my own.

Regards,
Monte Carver

[Alexander Bulei]

Hi MCarver,

The error occurs upon attempting to close the DialogEx

What do you have in OnClose event?

Best Regards.

[MCarver]

I am not using the OnClose Event. Best I can tell, this is a Javascript error, as the IW server is not hit.

[MCarver]

To further understand this problem, I have removed all but one IWCGJQEdit from my DialogEx, and the problem still persists. However, if I set for this edit control the SubmitOnAsync = False, then the error disappears. BUT of course my changes do not get submitted. Please note that this problem does NOT EXIST for the TCGJQMemoEx

More info.. I remove the TCQJQMemoEx and run again. NOW the error has disappeared. I have several other forms with this same problem, but i have NO IDEA why the error disappeared.

So what I am discovering?

Please Advise. Have I found a bug, or am I doing something wrong? Suggestions for resolving are greatly appreciated.

Regards,
Monte Carver

[Alexander Bulei]

Hi MCarver,

The fastest way to help you, doing the remote session if you have premium tickets, otherwise, send us the simple testcase project.

Best Regards.

[MCarver]

Alex,

I believe I finally found the problem. I had a DataSource OnChange event that was doing a ReloadGrid. This was the culprit that was causing the Exception. I never did understand why I would not consistently receive this error between identically designed frames.

The ReloadGrid was then occurring when the DialogEx was Opened. Any subsequent action raised the error (sometimes). The ReloadGrid of course is necessary when detail data of Master Data is being inserted/Modified thru the DialogEx. How would you suggest refreshing the grid? Currently I switched to having it fresh when the DialogEx is Saved/Canceled

Thanks your for consideration and time on this matter.
Monte Carver

[Alexander Bulei]

Hi MCarver,

I'm glad that you found the problem

Currently I switched to having it fresh when the DialogEx is Saved/Canceled

Yeah, I think it's a suitable place for it.
The session must be alive and component exists on page.

Best Regards.