This was brought to my attention recently and I was wondering if anyone had any insight on it. If we print a Priority Dispatch Report some job sequences will have the attached PO number, but most will not. It will just say PO: 0, despite having a PO number attached to that sequence. I downloaded and took a look at the SSRS report style and there is an IIF expression on that field, confirming that it will print a literal 0 in case the PO number was not found. Am wondering now exactly why those numbers aren’t being found. Is the Priority Dispatch Report perhaps driven by a BAQ that I could check out?
In the report style you should see the rdd that it’s based on.
Go open up that rdd and look.
Thanks Kevin that’s the place to look. You’re a great help as always. I’ll likely just mark your post as the solution as I don’t think I’ll find a solution for this.
Doesn’t seem like Priority Dispatch uses any BAQs. It does naturally refer to the PORel table. Just as a sanity check I wrote a BAQ to confirm these material/OP sequences do have PO numbers, they just don’t show up on the report.
Don’t give up hope yet.
Appreciate the encouragement. I might have to learn a thing or two about Report Data Definitions before I dig any deeper. I haven’t ever messed with those so far.
Took the “is nothing? then print as 0” expression off the PONum field in the SSRS report, uploaded it, as expected now it just doesn’t print the number at all. PO Number isn’t making it into the report for some reason. Evidently that is a step deeper in the system than the report itself…