Visual report not rendering correctly when "Show CS Adventure Requirements" selected

Scoutbook Scoutbook & Scoutbook Plus Bugs
, ,
1

When I create a basic advancement report, everything works fine (see first screenshot).

image
image1623×454 35.1 KB

However, once I select the “Show CS Adventure Requirements” option, I get the following catastrophe (see second screenshot).

image
image1908×584 32.7 KB

This option worked for me in prior years and was a useful report for diving down into specific requirements that were missing.

NOTE: Once it shows this way on the screen, I’m out of luck. Exporting it to a PDF or CSV includes much of the same nonsense: The PDF is identical while the CSV is full of HTML which should absolutely not be there.

In case it helps, the name of the report in question is AOL Progress Report v2.1 (detailed).

2

@DougFriedlander - please provide the ref number from the report.

4

I do not see the reference number for the report presented either on the list of custom reports nor on the report design page (see screenshot below). However, when I generate the report, I see the URL contains a parameter that might be the number you’re looking for: ReportID=2221660

In case it helps, here’s the full URL for the report: Report Builder - AOL Progress Report v2.1 (detailed)

image
image1676×947 91.4 KB

5

@DougFriedlander - the ref number is at the bottom of the generated report when you hit run.

6

I promise you it’s not. I already checked there the first time. Here’s a screenshot to show you I’m not crazy.

image
image1916×1037 72.9 KB

7

Oh wait. It’s so malformatted, it’s hard to see but maybe this is it…

image

8

@DougFriedlander - that is it I linked a similar post. The dev team was provided with the prior report. Watch the change log for when the fix is announced

9

Thanks. The one you linked only seems to address the HTML in CSV item I mentioned which was secondary to the primary issue which is that the main visual report (in the browser) is horribly mis-formatted. Will both issues be addressed in the fix you mentioned?

10

@DougFriedlander - I am not on the dev team and it is the html causing the issue.