Thought I had this working but it appears I was mistaken.
I’m working in an updateable BAQ using a BPM. My goal is to clear the UD15 table of its current data and then refill it with the new information that I would like to use. Currently, I am simply trying to clear the table out. My goal at the end of this is to have a completely empty UD15. I am using the query to fill the table and setting all rowMod to “D”. I’m then using the BO to UpdateExt on UD15. Is there something wrong with this setup or is there an easier way to do it? Any help would be greatly appreciated.
While this might be easier for a one time usage, unless I’m mistaken, this won’t work for what I’m doing as I’m hoping to add custom code after this to then populate the UD15 table. End goal would be to be able to run something that would clear the table and fill it with the new information without having to use a separate tool to clear the target table first.
No problem whatsoever. I appreciate the reply and I wasn’t overly clear. I’m not opposed to using a code block, but I’ve tried code in both BPM and Customization with the effect being that the code runs, appears to do something, but then when I check the table, the previous data is still there. I’m trying this way now since none of my code seems to have the desired effect.
Considered Using DeleteByID but I couldn’t get it to work in my code and as far as using the Invoke BO Method, I didn’t see a way to loop through the records to delete them all.
This reply was for another comment. I put it under the wrong one.
The first set of code appeared to work until I checked the UD15 with a separate BAQ which showed the old information still in it. Also if ran in a dashboard, it showed the old data. If ran in a BAQ, I received the same results as yours, until I checked it with the other or used it in the dashboard.
The second set of code I received the error Cannot implicitly convert type ‘void’ to Ice.Tableset.UD15Tableset
Also the error on the typo (DeletetByID) but that one I found easily but this one is eluding me more.
My mistake–the second query I pulled up to validate was one that was already in the system. Turns out it had a criteria to filter records that weren’t entered today. Whoops.
I’ll take a look again tomorrow if someone else doesn’t get to it first.
I tried this on a post process on GetList and it did not work. I then tried it as a base process on GetList and it worked! Thank you so much for your help.