The trigger shown is the BAQ dataview of UD08 being changed to another row that I clicked in the grid, and below shows that GetByID is triggered after I change a row. Do you mean the initial BAQ Dataview of NonConf?
If you click into there… it adds that dataset you’re seeing in debugger and that boogers everything up. Even if you don’t change any settings inside there… its too late!
AND… there’s no way to get it back OUT!!!
So… this sucks (every time this happens)… but… you need to delete your rest-erp action out of your event. Add it back in and rebuild it. And this time DON’T go into that Dataset area in the Response parameters.
Could be. Possible your GetByID is running before your baq dataview is populated. So it is trying to run (initially) without having any values to pass.
Is it when you load the TranID in NonConf? Or when you switch to your custom tab?
I ended up keeping all the information on the same tab. No seperate page. It happens after I click on the TranID on NonConf’s Landing page, when all the NonConf data fills and the BAQ dataview table fills, that’s when I get the record not found error. I’ll play around and attempt to trigger the GetByID after the baq dataview gets populated even though I think it already is.