columnFormat - wildcard numberformat taking precedence

[Wei Wang]

We noticed that in v2023.05 & v2023.10, the way Apliqo handles columnFormat has changed in respect to numberFormat. Previously, we could use a blank column name as a wildcard and also specify numberFormats specific to other columns. Columns which are not specified will take on the wildcard numberFormat. To specify a column, we can either use (a) the column index or (b) the column header display name.

In the newer versions, specifying a column using (b) method no longer works in conjunction with the wildcard when it comes to numberFormat.

Please refer to the example below using Apliqo_Demo (a2.v2 “Simple planning template” screen):

• add the following Adv Option under “table”

  • json "columnFormat": { "Jan": [ { "readOnly": false, "numberFormat": "#,###.00;(#,###.00);0" } ], "": [ { "readOnly": false, "numberFormat": "#,###;(#,###);0" } ] }

• the Jan column is not formatted with two decimal points

• if we use “4” as the column index instead of “Jan”, the column is formatted as expected

‌

[Ada Trajer]

Hi Wei, this issue has been resolved and the fix will be included in the nest release.