If a value in a document is "null", shouldn't a complex listing skip this?

Engines Print Engine
1

I am printing a complex listing, and some calculated values in the document are “null”. Should’t a complex listing skip these?

Fields marked in blue and yellow are “null” in the screenshotted JSON.

image
image857×329 23.2 KB

image
image339×120 2.67 KB

3

Hi @jasper-silent-root

I’ve just spoken to @rudi-clear-moss about this and you’ve bumped into a special aspect of the Print Engine.

The listing prints a row for each element in the data set. This means that you get a row for:

  • “KG”
  • “Bank_AuslEK”
  • “Bank_AuslStAnrechnung”
  • “Bank_GewSt452”
  • “Bank_SPIF_Ertraege”
  • … and any other rows in the data set which are relevant for this Listing

If you don’t want to print rows because the field value is null, then you need to remove the data point from the json completely. Normally empty values aren’t saved. null values can appear where a value is set and then deleted. This doesn’t usually cause an issue as A12 treats empty and null as equivalent.

There are a couple of ways forward for you:

  1. Clean the data before printing
  2. Raise a requirement ticket so that modelers can define the null handling in the listing for fields and groups.
4

We adopted number 1 from the two options listed above.