So is Epicor just messing with me?

I’m using a conditional that checks if this query has at least one result:

I’m then using the same query to fill a table:

The table though has zero rows. I know this because I then have a show message which displays a count of the rows in the table right after this. So if there are no rows in that query, it should be kicked at the conditional and never reach the show message. Instead it is passing through the conditional and then showing me the message which tells me there are count as 0.

If I run the query outside of the BPM (substituting the number that is running through the BPM which also shows on the show message), I have two records.

Hard to say without seeing the BPM conditions, the BAQ, and its results when you run it manually.

I’m sorry Andrew but I’m not sure what you are looking for. The condition, as stated, checks if the query has at least one result.
image
The BAQ is shown in the two pictures. The only criteria on the query is the one shown. PartNum = @parentPart argument variable.

A BAQ ran outside of the BPM with the same exact criteria results in two records.

I appreciate any help but am uncertain what additional information you are requesting.

Epicor is not messing with me. I am messing with me.

I rewrote this numerous times. In my frustration, I had created the same variable twice with different capitalization. Was putting my count into totalParts and calling TotalParts for my check.

I blame it on being late afternoon and too many hours without coffee. Thank you @andrew.johnson for attempting to help sort things out.

2 Likes