Crystal Reports Job Traveler changes are working, but only for one Part

Guys I’m not sure what I did here.
I added 3 things to an existing Crystal Reports job traveler.

To the RawMaterialComponent subreport, linked via JobMtl.PartNum:

  1. text field with PlantWhse.PrimBin

To the main report, linked via JobHead.PartNum
2. text field with CustXPart.XPartNum
3. picture Content blob from FileStore.Content (we just use the PartNum as the ImageID)

This works perfectly…for the handful of jobs that exist for the Part I chose at random while I was building the thing. I just went into Image maintenance and picked one we had an image for, and checked in Part Advisor to make sure we had produced it. For those handful of jobs, this thing works beautifully. For everything else (that I have tested so far) it comes up blank.

I’m not even sure which thread to pull. I tested each item as I was developing it, I had no reason to think it wouldn’t work with other parts…

Edit:
I should also add that I did make sure the other parts I’m testing do have both the customer xparts and the associated images.

Also I can confirm from the jobs that do print correctly, not all of the raw materials have a primary bin. That does not seem to be the issue.

What do you mean by “it comes up blank”?

Here’s the main report in CR:

Here’s a working example (redacted):

And here’s “blank”:

Thanks. Was not sure if you meant the whole report or just images.

Since it works with a part that has an image, I would double check the joins to make sure that is correct. It sounds like the join to the Image table is what the problem is.

1 Like

I appreciate your help. I figured out what happened. What I’m less certain of is whether we’re doing this “correctly.”

When we first started setting up part images, we were going into Image Maintenance and creating a new image using the PN as the image ID, and then linking that to the part master. 2 steps. And that’s the way I did my joins:
JobHead.PartNum > Image.ImageID
Image.ImageFileName > FileStore.FileName

But then I discovered if the job part doesn’t have a corresponding ImageID, we get the blank report above.

So my coworker created a “blank” image and then linked that to ALL the mfg parts that don’t (yet) have images. But they did it by going into Part Entry and manually linked them to an image with ImageID = ‘blank’ which hoses our joins.

In the end, we decided to just manually create ImageIDs for all the mfg PNs, and it’s working.

But, I’m really not clear why we were getting a blank report whenever there is a null value on FileStore.Content to being with. Why doesn’t it just print a blank blob?

Signed,
Blank Blob