When I am creating a chart on my Active Report Dashboard, it looks great in the preview. But when I run it, the X Axis is gone and replaced with the Legend (series). I've tried reversing this (my co-worker had to do this and it worked) but it didn't work on mine. Even if it did, I'm not sure that's a cure-all fix to what the issue may be.

This message has been edited. Last edited by: <Kathryn Henning>,

Hello,
Unfortunately you hit a known unsupported syntax for Active Charts.
In your procedure you have either ACROSS syntax Or GRLEGEND 1. It is documented in Active Technologies User's Guide
That ACROSS is not supported

  http://infocenter.informationb...eTech/launch_pdf.htm  

Creating an Active Technologies Chart section on page 357.

ACROSS syntax gets generated in the procedure for Charts, when you place a field in the Legend bucket.

The reason why preview shows up correctly, is because preview is in HTML5(JSCHART) format. But the Runtime is in Active format.

Thank you.
Nick.

quote:

When I am creating a chart on my Active Report Dashboard, it looks great in the preview. But when I run it, the X Axis is gone and replaced with the Legend (series). I've tried reversing this (my co-worker had to do this and it worked) but it didn't work on mine. Even if it did, I'm not sure that's a cure-all fix to what the issue may be.

Yes, we encountered the same issue here. Opened a case with IBI and received the response back:

----------------------------------------------------------------------------------------------------

"...the issue here is that Active Reports output (AHTML) does not support ACROSS.

http://documentation.informati...h/wf77activetech.pdf

Page 238:
The output formats (AHTML,FLEX,APDF) support BY syntax in the GRAPH Procedure.
Does not support ACROSS syntax.
Make sure to code your GRAPH FILE Procedures using BY.
----------------------------------------------------------------------------------------------------

Now, as you and I both know, when you're using InfoAssist, it creates the code, not you the user. Hoping that this gets fixed in an upcoming release.