I’ve added a UD31 grid in the Receipt Entry > Details screen. Adding lines works fine — the data is saved correctly in the UD31 table (confirmed using a BAQ).
The problem is with deleting lines. Sometimes when I delete a line from the grid, it disappears from the screen but still shows up in the UD31 table. Other times, the line stays in the grid and the database even after trying to delete it.
If I add a new line and then delete it right away, it works as expected — the line is removed from both the screen and the database. The issue mainly happens with existing records or when I reopen the screen.
What I want is: whenever I delete a line from the UD31 grid, it should be removed from both the screen and the UD31 table every time. If anyone has any ideas or has faced this before, please let me know.
Hi @vsamit, sorry, I must have missed your last post come through.
On my DeleteByID rest call, I don’t have any Request or Response parameters at all. I’m just sending the (5) keys in my Method Parameters. Try deleting your Request Parameters and see if that works.
You may have to completely delete your rest widget and create it again. Sometimes going into the Dataset settings causes it to break.
Making an assumption here… in your last screen shot, your UD16.Key1 box is read only. Usually this happens when a dataview hasn’t been initialized yet. So, I’m wondering if your “GetaNew” is not responding the way it should.
Can you verify in debugger that you are getting a response from that rest call… and what you’re getting?
Here is my “GetaNew” Preview and Response:
Can you show me your settings in your “GetaNew” rest call widget?
That didn’t change my results with those changes. I haven’t used debugger much. I clicked in the event screen and selected control + alt + 8 and nothing came up.
Ice.Proxy.BO.UserTracingImpl
GetNewOrGetByID
https://posiaamerpe1001.positronic.local/EpicorERPPilot/
Ice.BO.UserTracingDataSet
4/10/2025 13:58:43:4164058
1
1eba682c-91c5-4cee-950c-a36d55295757
0
Ice.Proxy.BO.UserTracingImpl
Update
https://posiaamerpe1001.positronic.local/EpicorERPPilot/
System.Void
4/10/2025 13:58:43:6313905
1
7c9ac5a4-47fb-4b65-9b5f-0a9d4017a640
0
ADMJBass
Off
Off
0
Off
false
false
false
false
false
false
Off
Off
Off
Off
Off
Off
Off
Off
Off
D:\Users\jbass\AppData\Roaming\epicor\log\
%appdata%\epicor\log\
4317108100
bab21538-c004-44b0-814a-c9452a1b1b42
false
0
Ice.Proxy.BO.UserTracingImpl
GetNewOrGetByID
https://posiaamerpe1001.positronic.local/EpicorERPPilot/
Ice.BO.UserTracingDataSet
4/10/2025 13:58:56:4257950
1
17c34e5f-2b76-49a3-88a0-37891d5131d2
0
In the browser’s Dev Tools you can see all the details of events firing in the console. You can also see all the request and response data being passed back in forth to the server:
Its just a MUCH MUCH MUCH more effective tool vs. the meager debugger in the Client.
If you CAN get access to the browser, then yes, you may not be able to open some forms that your company has locked down to Classic only. But if you’re designing for Kinetic forms, its worth jumping into the browser and opening App Studio there so you can use the browser’s dev tools as you work. Maybe you could ask for browser access in your Pilot environment only?
There is a way to turn on the browser debug tools for the smart client windows. I did it in one of the instructor led training courses I took (probably on BPMs) but I can’t find any documentation and I haven’t been able to figure out how to do it again (in the last half hour). We do everything in the browser so it hasn’t been a need.
@rossin82 Follow those above steps and it looks like you can use the debugger in the Client! As it states, it will open the debugger in its own window. Nice.
