Crosstab chart not displaying the same in Sage 300 as in Crystal Reports

[former_member759204]

I have created a report in Crystal Reports 2016. It works like a charm when run from within Crystal Reports.

When I try to generate the same report from within the Sage 300 2020 program, the chart portion does not display all the periods of the report. The cross-tab in the report show all the periods, so I know that the info is filtering correctly in the record selection.

It is just the chart with the issue, and it will only show 9 of the 12 months (across 4 years) it is supposed to.

To be more specific, I am pulling records for the current plus past 3 fiscal years. My cross tab has data for ALL periods that have transactions (which are all periods from the current period and back), which do appear to be correct. The chart is based on the crosstab - on change of year, subdivided by period, showing the sum of @salesLessRet formula. However, the chart when run within Sage only shows periods 1,2,4,5,6,7,8,9,10. No period 3 or periods 11-12 - all of which show data in the crosstab portion of the report.

I have tried saving it with an older version of Crystal reports thinking maybe it is a compatibility issue since I believe Sage 300 2020 is built using Crystal 2013 viewer, but so far this has not worked.

If anybody has come across this before, or has any suggestions, I would love to hear your feedback. Running it manually from within a Crystal Reports viewer is not an option at this time as it needs to be automated using the existing software from within Sage.

Thanks.

Jody

[former_member759204]

to be more specific, this may be where the problem is, but I can't figure out why..

This is located in Cross-Tab Group Options - Customize Group Name Field using a formula...

numbervar per;

if {OESHDT.AUDTORG} = "CANDAT" Then

(select {OESHDT.PERIOD}

Case 1: "August"

Case 2: "September"

Case 3: "October"

Case 4: "November"

Case 5: "December"

Case 6: "January"

Case 7: "February"

Case 8: "March"

Case 9: "April"

Case 10: "May"

Case 11: "June"

Case 12: "July"

Default: "Other")

else if {OESHDT.AUDTORG} = "USADAT" Then

(select {OESHDT.PERIOD}

Case 1: "May"

Case 2: "June"

Case 3: "July"

Case 4: "August"

Case 5: "September"

Case 6: "October"

Case 7: "November"

Case 8: "December"

Case 9: "January"

Case 10: "February"

Case 11: "March"

Case 12: "April"

Default: "Other")

else if {OESHDT.AUDTORG} = "MRIDAT" Then

(select {OESHDT.PERIOD}

Case 1: "May"

Case 2: "June"

Case 3: "July"

Case 4: "August"

Case 5: "September"

Case 6: "October"

Case 7: "November"

Case 8: "December"

Case 9: "January"

Case 10: "February"

Case 11: "March"

Case 12: "April"

Default: "Other")

else if {OESHDT.AUDTORG} = "HKGDAT" Then

(select {OESHDT.PERIOD}

Case 1: "August"

Case 2: "September"

Case 3: "October"

Case 4: "November"

Case 5: "December"

Case 6: "January"

Case 7: "February"

Case 8: "March"

Case 9: "April"

Case 10: "May"

Case 11: "June"

Case 12: "July"

Default: "Other")

else "NOINFO)"

[former_member759204 · Accepted solution]

I ended up needing to insert a second cross-tab report that essentially displays only the period labels, and removed the custom name labels on the rows as the default names. It is messy, and doesn't translate the period names to the chart, but at least there is a reference on the same page, and at least the chart appears to display the correct information now.

What is also strange, is that the custom column labels do not appear to cause any issues at all. Just the row labels.

[ido_millet]

Insert, Chart...
and select the option to base the chart on the CrossTab.

If that fixes the issue, then the problem is that your current chart grouping logic doesn't match the CrossTab grouping logic.

[former_member759204]

But I don't have the logic in the chart, it generates automatically based on the names in the cross-tab. If there is a place in the chart where I can specifiy this can you please tell me. I can't find anything...

The names and data display correctly in the cross-tab.

Thank you

.Jody

[DellSC]

Unfortunately, we have no way of knowing how the SDK was implemented in Sage or which runtime was used. Your best bet is going to be to contact Sage support to try to resolve this since the issue is in their software.

-Dell

[former_member759204]

Does this help?

SP23 for SAP Crystal Reports® runtime engine