Closed SDScandrettKint closed 3 weeks ago
More helpful log from Firefox:
@SDScandrettKint @csmith-he - disabling paging in the table config fixes the issue, so it is something to do with paging. There are a couple of other reports/scenes that use paging and my very limited testing does not show the same error, but I suggest it is checked.
Note: this issue is not specific to just associated consultations, but any associations that use the relatedResourceTwoColumnTableConfig
table e.g. Consultations, Activities, Digital Files etc.
Update: nevermind, it affects all tables in resources.js
, as Associated Mons/Areas/Artefacts is also affected which has the table type relatedResourceThreeColumnTableConfig
. Strangely, the associated Application Areas table is not affected, which comes from it's own file application-area.html
/ .js
Adding an associated consultation in an Application Area causes report to break