Json data in table does not display in PDF reports

[OwenTC]

Json data in tables in xsoar does not show up when I try to export the table to a pdf report.  I'm wondering if anyone else has had this issue or possibly has an alternative way to display this data in a report.  (see attached screenshots)

Thanks!

[asawyer]

Hi @OwenTC – I am not having this issue with reports, but the table in my war room entry also looks different when I try to replicate the issue. (It looks like your JSON values that get populated in the table cells contain newlines, and I am not able to replicate this.)

What XSOAR version and build are you on? Also could you please share the exact JSON you are passing in to the JsonToTable command? (Feel free to replace the data values with dummy data but please keep the data structure the same.)

[OwenTC]

Hi @asawyer 

I am on XSOAR version 6.12

Build version: 857430

Here is the exact JSON being passed

[ { "auth_results": { "dkim": { "domain": "example.com", "result": "pass", "selector": "example" }, "spf": { "domain": "example.com", "result": "fail" } }, "identifiers": { "header_from": "example.com" }, "row": { "count": "1", "policy_evaluated": { "disposition": "none", "dkim": "pass", "spf": "fail" }, "source_ip": "xx.xx.xx.xx" } }, { "auth_results": { "dkim": [ { "domain": "example.com", "result": "pass", "selector": "example" }, { "domain": "example.com", "result": "pass", "selector": "example" } ], "spf": { "domain": "example.com", "result": "fail" } }, "identifiers": { "header_from": "example.com" }, "row": { "count": "1", "policy_evaluated": { "disposition": "none", "dkim": "pass", "spf": "fail" }, "source_ip": "xx.xx.xx.xx" } } ]

is_auto_json_transfer is set to "True"

[asawyer]

@OwenTC Hm something is modifying the data so I am unable to test with the same data. (Please see the screenshot below – my entry looks different than yours.) Are you passing in any other arguments to JsonToTable? Could you download and share the war room entry that is having this problem? (Should be a markdown file.)

 

[OwenTC · Accepted solution]

@asawyer I opened a support case in parallel to this post and they informed me that the fix for this is to upgrade the base pack to version (1.33.47).

I have tested this and it now works as expected

Appreciate your help!