webstaff reporter: nullability selection sometimes doesn't take

[Galen Charlton]

The web staff client doesn't always seem to recognize the nullability selection if more than one join is in play. For example, try this:

- Create a new report template
- Use ILS User as the base source and check the nullability checkbox.
- Expand to All Circulations, then to Circulating Copy. Set "Child nullable" as the join type for circulating copy.
- Add the copy barcode field.
- Note that the source path is "ILS User -> All Circulations (inner) -> Circulating Item (inner)" when it should be "ILS User -> All Circulations (inner) -> Circulating Item (left)"

Note that if you go up and explicitly set the nullability of the All Circulations link to "Default", then go back and add the barcode field again, the correct join path is achieved.

Evergreen master (and probably rel_3_0)

[Galen Charlton (gmc)]

(Note that successfully testing reports that use joins on virtual fields requires the fix for bug 1721807.)

[Beth Willis (willis-a)]

EG 3.5.1

I followed Galen's recommended steps in creating a template, but could not replicate this problem.

My source path is "ILS User -> All Circulations -> Circulating Item (left)", though. (Please see screenshot attached.) I don't know if the default join type for All Circulations is "inner."

Note: I did not explicitly set the nullability of the All Circulations link to "Default"; it was set to "Default" by default.

[Susan Morrison (smorrison425)]

I followed the steps on 3.8 and also could not replicate the issue (screenshot attached).

For line 1, I left All Circulations as Default and chose Child Nullable for Circulating Item, which resulted in ILS User -> All Circulations -> Circulating Item (left)

For line 2, I changed All Circulations to None Nullable (inner) and kept Circulating Item as Child Nullable, which resulted in ILS User -> All Circulations (inner) -> Circulating Item (left)