Hi Will,

The null values will display as <0> when the first table has a zero for a value that has no corresponding value in the second table. So if the first table had a value of 123 and there was no corresponding value in the second table, you would get a result of <123> rather than null.

So if you have null values in the first table, rather than setting it to 0, you should set it to "null". This will return null values rather than <0> in the results.

Please let us know if you have any further questions.

Regards,

Jon

Hi Jon,

Thanks for your answer. You were complete correct that I actually had 0 values rather than null in my fk fields. I have fixed that, and now I get blank cells rather than "<0>". This is an improvement, however an answer to my original (rather poorly framed) question still would be useful to me -- can I supply some text to be displayed when the fk field is null?

thank you,
-Will

Hi Will,

I confirmed that anything you enter into that FK field will come back with the bracketed response when there is no matching value, like 123 coming back as <123>. So the only options are to either expect bracketed responses if you decide to fill in anything in the FK field or you just leave it blank. Beyond this, the only thing you could do to prevent anything from coming back is to have some custom javascript code to modify the UI to omit the response if it comes back with a value you want to hide. So if you went back to using zeros, your javascript would hide anything coming back that would normally display <0> in the response.

Does this make sense?

Regards,

Jon