I have a weird issue with form. I have a form named X. It has almost similar design of PurchTable form. So, as usual form X also have datasources for its header and lines.
Now, when I mark more than one record on the line grid and try to delete, the form goes to "Not responding" state. And apparently no line gets deleted. But it works fine for one record.
I have debugged the form. I have found that the debugger hits the Line datasource > delete() and keeps on running that method again and again and never comes out of it.
Can anyone of you tell me what may be the reason of such behavior of the system? What should I follow to fix this issue?
Thanks in advance!
What's the call stack of the repeated calls of delete()?
The calls stack is as follows:
However, debugger doesn't come out of Datasources\PurchLine\Methods\delete() . It keeps on running from line 1 of this method through last line.
do you have task method overridden in the form? and some Code calling delete inside presumably?
Yes, task method in form is overridden. But delete() is not being called explicitly from any of this flow.
If you put breakpoint in the task method, what is the call stack then? Seems like something a bit farther away might be causing this.
just for test's sake, can you remove the overridden Task method, and run the form again?
It will be interesting to see, if the error still persists.
I have tried that. Unfortunately there is no change in behavior.
After further investigation, I can notice the debugger goes to table delete() only once. And rest of the time the super() in datasource > delete() doesn't even hit table > delete().
What about the delete actions in your tables? Do you have some?
Hi Nikolaos, it is actually PurchLine table. So, it has many deleteActions which are standard tables.
in that case, I'll remove the datasource delete method, and test again..
also try Clearing all usage data connected to this form/table.
I already asked: "If you put breakpoint in the task method, what is the call stack then? Seems like something a bit farther away might be causing this."
Did you look into this?
I could rectify the problem. Someone had called active() from the data source delete() method which was probable reason of this weird behavior of the system. I have just removed that code and now this is working perfect.
Thank you all for your support! :)
Business Applications communities