Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CE10 : Bugs (Reasons Why & WorkArounds)

Status
Not open for further replies.
bzzyplayin

bzzyplayin

Programmer
Jan 4, 2001
16
US
We recently converted from 8.5 to 10. With the conversion, I have discovered a few bugs that I wanted to share with all of you since I had to figure out what was causing the issue(s) on my own. Crystal (Business Objects) was no help at all!

Reports with comments in the record selection fail (the pageserver shuts down immediately upon viewing the report). Solution: Removing the comments (//) takes care of this issue.

Reports using V10’s new drilldowngrouplevel function to control whether the section is visible or not produces the error “Information is needed before this report can be processed”. This only occurs on scheduled reports that contain a sub-report when the drilldowngrouplevel is used on that section. There is no issue when viewing on demand. However, since my report is large, I didn’t want the users to have to hit the database multiple times. Therefore, I had to modify the report by inserting another grouping (etc.) in order to use the “traditional” Hide (Drill-Down OK) option.

Besides the few bugs mentioned, we are happy (overall) with this version and would recommend it. There are a lot of useful features, etc.
 
Sort by date Sort by votes
HI,
We have never experienced that 'bug' about comments since our migration from 8.5 to 10 : for instance, this:
Code: 
({WR_REPORT.WORK_REQUEST_TYPE} = "MAINT" or {WR_REPORT.WORK_REQUEST_TYPE} = "TEREQ") and 

//Systems may have multiple highway milepoints this allows only the primary to be used. 
{SYSTEM_THRU_HIGHWAY_LOOKUP.PRIMARY_FLG} = "Y" and

{SYSTEM_DEFINITION.SYSTEM_IND} = "L" 


AND (If {?County} <> "ALL"  then Cstr({SYSTEM_DEFINITION.COUNTY_CODE}, 0) = {?County} else True)

AND (If {?District} <> "ALL"  then {SYSTEM_DEFINITION.DISTRICT_CODE} = {?District} else True)
 
AND (If {?PriorityCode} <> "ALL"  then Cstr({WR_REPORT.PRIORITY}, 0) = {?PriorityCode} else True)

AND (If {?FeedPoint} <> "ALL"  then {SYSTEM_DEFINITION.FEEDPOINT_NO} = {?FeedPoint} else True)

AND (If {?LMaintZone} <> "ALL"  then {SYSTEM_DEFINITION.MAINT_ZONE} = {?LMaintZone} else True)

AND (If {?Municipality} <> "ALL"  then {SYSTEM_DEFINITION.MUNICIPALITY_CODE} = {?Municipality} else True)


AND 

  (If {?EmpNbr} = "ALL"  then
    True
  else if {?EmpNbr} = "NONE"  then
    (IsNull ({WR_REPORT.EMPLOYEE_NO}) or ({WR_REPORT.EMPLOYEE_NO} = {?EmpNbr}))
  else
    ({WR_REPORT.EMPLOYEE_NO} = {?EmpNbr}))


AND

(If {?HistoryFlag} = "ALL"  then
   True
 else if {?HistoryFlag} = "active"  then
   {WR_REPORT.HISTORY_FLG} = 'N'
 else if {?HistoryFlag} = "history"  then
   {WR_REPORT.HISTORY_FLG} = 'Y')

AND

(If {?ReportedAsCode} = "ALL"  then
     True
 else if {?ReportedAsCode} = "Knockdown"  then
     {WR_REPORT.REPORTED_AS_CODE} in ['KD', 'BAS', 'KDM', 'KDC', 'KDP', 'PLL']
 else if {?ReportedAsCode} = "LightsOut" then
    not ({WR_REPORT.REPORTED_AS_CODE} in ['KD', 'BAS', 'KDM', 'KDC', 'KDP', 'PLL'])
 else if {?ReportedAsCode} = "Breaker" then
    {WR_REPORT.REPORTED_AS_CODE} in ['BT', 'CDC', 'SCR', 'CD', 'OUT'])

AND

(If {?CompRept} = "N" then
   True
 else if {?CompRept} = "R" then
   ({WR_REPORT.REPORTED_AS_DATE} in Date({?StartDateStr}) to Date({?EndDateStr}))
 else if {?CompRept} = "C" then
   ({WR_REPORT.WORK_REQUEST_COMPLETION_DATE} in Date({?StartDateStr}) to Date({?EndDateStr})))

works fine..We require our developers to comment their code when needed to clarify what it is doing.

[profile]




 
Upvote 0 Downvote
I should have clarified, the issue occurred when select case statements were commented out. I will provide a sample tomorrow of the selection criteria that I used (to test that theory).

Note: As soon as I removed the commented code, the report was viewable without taking down the page server. However, we have since applied patches. Therefore, that issue might have been addressed by now.
 
Upvote 0 Downvote

Update: I published the report to our test server (after all of the patches have been applied and the same problem occurred).

Note: We also use comments to document our code. There are no problems when we use text as comments. We only run into the problem when actual code is commented out. See below. The comments that are just text work fine. It's the last chunk of code that causes the problem. As soon as I remove it, all is good.

Note: Let me know if this happens for you when you comment out code. I am now really curious : )

Code: 
{FCGAMFBD.FGFCHRTSEC} = '2' 
and
((Select {?Reporting Basis}
    Case 'M' : (Select {?Level} //Open Stores
               Case 'R' : (Select {?Level Value}
                          Case 0  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFSTRNUM} < 900
                          Default : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFREGNUM} ={?Level Value} and
                                    {FCGAMFBD.FGFSTRNUM}< 900)
               Case 'D' : (Select {?Level Value}
                          Case 0  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFREGNUM} in [1 to 8] 
                          Default : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFREGNUM} in [1 to 8] and
                                    {FCGAMFBD.FGFDSTNUM} = {?Level Value} and
                                    {FCGAMFBD.FGFSTRNUM} < 900)
               Case 'S' : (Select {?Level Value}
                          Case 0  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFSTRNUM} < 900
                          default  :
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFREGNUM} in [1 to 8] and
                                    {FCGAMFBD.FGFSTRNUM} = {?Level Value})
               Default  : 
                          {FCGAMFBD.FGFLEVEL1} =2 and
                          {FCGAMFBD.FGFREGNUM} in [1 to 8] and
                          {FCGAMFBD.FGFSTRNUM} < 900)
    Case 'A' : (Select {?Level} //Active Regions
               Case 'R' : (Select {?Level Value}
                          Case 0  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL3} > 0
                          Default : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} = {?Level Value} and
                                    {FCGAMFBD.FGFLEVEL3} > 0)
               Case 'D' : (Select {?Level Value}
                          Case 0  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} in [1 to 8] and
                                    {FCGAMFBD.FGFLEVEL3} > 0
                          Default : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} in [1 to 8] and
                                    {FCGAMFBD.FGFLEVEL3} = {?Level Value})
               Case 'S' : (Select {?Level Value}
                          Case 0  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} in [1 to 8] and
                                    {FCGAMFBD.FGFLEVEL3} > 0 and
                                    {FCGAMFBD.FGFLEVEL4} > 0
                          Default  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} in [1 to 8] and
                                    {FCGAMFBD.FGFLEVEL3} > 0 and
                                    {FCGAMFBD.FGFLEVEL4} = {?Level Value})
               Default  : 
                          {FCGAMFBD.FGFLEVEL1} =2 and 
                          {FCGAMFBD.FGFLEVEL2} in [1 to 8] and
                          {FCGAMFBD.FGFLEVEL3} > 0 and
                          {FCGAMFBD.FGFLEVEL4} > 0)
    Case 'L' : (Select {?Level} //All
               Case 'R' : (Select {?Level Value}
                          Case 0  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} > 0
                          Default : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} = {?Level Value})
               Case 'D' : (Select {?Level Value}
                          Case 0  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} > 0 and
                                    {FCGAMFBD.FGFLEVEL3} > 0
                          Default : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} > 0 and
                                    {FCGAMFBD.FGFLEVEL3} = {?Level Value})
               Case 'S' : (Select {?Level Value}
                          Case 0  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} > 0 and
                                    {FCGAMFBD.FGFLEVEL3} > 0 and
                                    {FCGAMFBD.FGFLEVEL4} > 0
                          Default  : 
                                    {FCGAMFBD.FGFLEVEL1} =2 and
                                    {FCGAMFBD.FGFLEVEL2} > 0 and
                                    {FCGAMFBD.FGFLEVEL3} > 0 and
                                    {FCGAMFBD.FGFLEVEL4} = {?Level Value})
               Default  : 
                          ({FCGAMFBD.FGFLEVEL1} =2 or 
                          ({FCGAMFBD.FGFLEVEL1} = 3 and {FCGAMFBD.FGFSTRNUM} = 50011)) and
                          {FCGAMFBD.FGFLEVEL2} > 0 and {FCGAMFBD.FGFLEVEL3} > 0 and
                          {FCGAMFBD.FGFLEVEL4} > 0))) //and

//The code below is no longer needed. 

//if ({FCGAMFBD.FGFFYEAR} = {CRPFIN.CURRYR4}) then
//   (if ({?Report Type} = 'M' and {CRPFIN.CURRPER} = 1) then
//        ({FCGAMFBD.FGFACTFP01} <> 0 or {FCGAMFBD.FGFBDGFP01} <> 0)
//    else if ({?Report Type} = 'M' and {CRPFIN.CURRPER} = 2) then
//        ({FCGAMFBD.FGFACTFP01} <> 0 or {FCGAMFBD.FGFBDGFP01} <> 0 or
//        {FCGAMFBD.FGFACTFP02} <> 0 or {FCGAMFBD.FGFBDGFP02} <> 0)
//    else if ({?Report Type} = 'M' and {CRPFIN.CURRPER} = 3) then
//        ({FCGAMFBD.FGFACTFP01} <> 0 or {FCGAMFBD.FGFBDGFP01} <> 0 or
//        {FCGAMFBD.FGFACTFP02} <> 0 or {FCGAMFBD.FGFBDGFP02} <> 0 or
//        {FCGAMFBD.FGFACTFP03} <> 0 or {FCGAMFBD.FGFBDGFP03} <> 0)

// The remaining periods have been deleted to save space (for posting purposes)

//    else if ({?Report Type} = 'Q' and {CRPFIN.CURRPER} = 1) then
//        ({FCGAMFBD.FGFACTFP01} <> 0 or {FCGAMFBD.FGFBDGFP01} <> 0 or
//        {FCGAMFBD.FGFACTFP02} <> 0 or {FCGAMFBD.FGFBDGFP02} <> 0 or
//        {FCGAMFBD.FGFACTFP03} <> 0 or {FCGAMFBD.FGFBDGFP03} <> 0)
//    else if ({?Report Type} = 'Q' and {CRPFIN.CURRPER} = 2) then
//        ({FCGAMFBD.FGFACTFP01} <> 0 or {FCGAMFBD.FGFBDGFP01} <> 0 or
//        {FCGAMFBD.FGFACTFP02} <> 0 or {FCGAMFBD.FGFBDGFP02} <> 0 or
//        {FCGAMFBD.FGFACTFP03} <> 0 or {FCGAMFBD.FGFBDGFP03} <> 0 or
//        {FCGAMFBD.FGFACTFP04} <> 0 or {FCGAMFBD.FGFBDGFP04} <> 0 or
//        {FCGAMFBD.FGFACTFP05} <> 0 or {FCGAMFBD.FGFBDGFP05} <> 0 or
//        {FCGAMFBD.FGFACTFP06} <> 0 or {FCGAMFBD.FGFBDGFP06} <> 0))

// The remaining quarters have been deleted to save space (for posting purposes)

//else
//    ({FCGAMFBD.FGFACTFP01} <> 0 or {FCGAMFBD.FGFBDGFP01} <> 0 or
//    {FCGAMFBD.FGFACTFP02} <> 0 or {FCGAMFBD.FGFBDGFP02} <> 0 or
//    {FCGAMFBD.FGFACTFP03} <> 0 or {FCGAMFBD.FGFBDGFP03} <> 0 or
//    {FCGAMFBD.FGFACTFP04} <> 0 or {FCGAMFBD.FGFBDGFP04} <> 0 or
//    {FCGAMFBD.FGFACTFP05} <> 0 or {FCGAMFBD.FGFBDGFP05} <> 0 or
//    {FCGAMFBD.FGFACTFP06} <> 0 or {FCGAMFBD.FGFBDGFP06} <> 0 or
//    {FCGAMFBD.FGFACTFP07} <> 0 or {FCGAMFBD.FGFBDGFP07} <> 0 or
//    {FCGAMFBD.FGFACTFP08} <> 0 or {FCGAMFBD.FGFBDGFP08} <> 0 or
//    {FCGAMFBD.FGFACTFP09} <> 0 or {FCGAMFBD.FGFBDGFP09} <> 0 or
//    {FCGAMFBD.FGFACTFP10} <> 0 or {FCGAMFBD.FGFBDGFP10} <> 0 or
//    {FCGAMFBD.FGFACTFP11} <> 0 or {FCGAMFBD.FGFBDGFP11} <> 0 or
//    {FCGAMFBD.FGFACTFP12} <> 0 or {FCGAMFBD.FGFBDGFP12} <> 0)

Note: The fields are from a Lawson table (on DB2).
 
Upvote 0 Downvote
Hi, OK I tested a simple example but had no problems with it, so I expect it to apply to more complex ones as well..
Code: 
//First use all Employees - comment out next 2 lines
//{MNDOT_EMPLOYEE.EMPL_STAT_CD} = 'A'
//and
{MNDOT_EMPLOYEE.DEPT_NBR}[4] = '3'

The commented selection causes no issues..
Note: In your posted code, unless there is a typo, you have a trailing and ({FCGAMFBD.FGFLEVEL3} > 0 and
)
before the commented code segment..This would cause an error .

[profile]
 
Upvote 0 Downvote
I deleted some sections of the code to shorten the post (I wasn't extermely careful on deleting the code). I thought it might not be clean. Sorry about that.

The statement does work fine when simply removing the last section of code (from the actual RPT file). Including the "//and" on the line before the HUGE commented code segment.

Well... Now I am curious though if it's a problem with nested case statements being commented out or what part of the commented code fails. I'll create a simple report and test it out (since your test was successful).

By the way, did you try to create the other scenario?
 
Upvote 0 Downvote
Hi,
Nope..I am not familiar enough with the new features yet to have tried it out.

[profile]

 
Upvote 0 Downvote
Hi,

bzzyplaying....how exactly did you get the drill down to work with converted reports that have sub-reports in them?

We're currently converting from Info7.5 to CE10 and, as you rightly say, the scheduled instances will not always drill down and come up with errors (I say "not always" as they sometimes work okay ?!?!)

Did you need to fix the sub-reports or the main report?

Any information would be gratefully received as this problem has caused the migration to come to a complete standstill as most of our reports rely on sub-reports.

Thanks in advance.

Bigal (MIS)
Virgin Retail
 
Upvote 0 Downvote
bzzyplaying....how exactly did you get the drill down to work with converted reports that have sub-reports in them?
Click to expand...
Did this part not answer your question?
Therefore, I had to modify the report by inserting another grouping (etc.) in order to use the “traditional” Hide (Drill-Down OK) option.
Click to expand...

Kingfisher [CECP]
 
Upvote 0 Downvote
Not really Kingfisher.

Not sure exactly what bzzyplaying means by :

Therefore, I had to modify the report by inserting another grouping (etc.) in order to use the “traditional” Hide (Drill-Down OK) option.
Click to expand...

Does this mean I need to remove the current groupings and re-create them? or is there a simple switch/flag that can stop the report using the drilldowngrouplevel function?

Still new to this so please ignore my ignorance if I being a bit thick [rednose]

Bigal (MIS)
Virgin Retail
 
Upvote 0 Downvote
Bigal - What errors are you seeing? Are you getting different errors when you "View on demand" versus "View latest instance"? Also, on the reports that produce the errors, is the sub-report visible immediately or only when the user drills down from the main report?

I actually ran into various odd issues when migrating to V10. I didn't keep track of all of them; I wish I would have so that I could share my experience with all of you. The 2 issues that I reported were the major ones that took up a lot of my time troubleshooting to determine what was triggering the errors.

There were a few things that I did though with the reports that contained sub-reports. I 1st opened them in the Developers tool & performed the "verify database" option on the main report & then did the same thing on the sub-report. I then re-published them to Crystal Enterprise to test the functionality.

For those that still produced errors, I published them various ways to see what options were triggering the error(s). I ran into the problem where I could view the report "on demand" but couldn't view a scheduled instance. What I found here was, when upgrading to version 10 I used the new function called "drilldowngrouplevel" to control when a section was visible. I used this method instead of controlling it using variables or using the Hide (DrillDown OK) option. For one of my reports I had to re-design it to use the traditional Hide(DrillDown OK). Note: The other reports required no design changes to resolve the errors.

Let me know if you still run into problems and I'll do what I can to help.
 
Upvote 0 Downvote
Hi bzzyplaying,

Errors that I'm getting are only on scheduled instances, not in CR10 or in preview. The errors are :

Information is needed before this report can be processed.

and

Unable to connect: incorrect log on parameters. File ~ce78c3b97305cd9d9.rpt.

A typical scenario is : I open the instance(has sub-reports at this level)-no problem, I drill-down one level(has sub-reports at this level)-no problem, I drill-down one more level(has sub-reports at this level)-ERROR. Close the report and re-open(has sub-reports at this level)-no problem, I drill-down one level(has sub-reports at this level)-ERROR.
It seems that as soon as I get an error, if I re-open the report it errors out as soon as I perform a drill-down.

There were a few things that I did though with the reports that contained sub-reports. I 1st opened them in the Developers tool & performed the "verify database" option on the main report & then did the same thing on the sub-report. I then re-published them to Crystal Enterprise to test the functionality.
Click to expand...

Done this.....still get the errors [sad]

Double checked the grouping and the drilldowngrouplevel is not used, instead we use the variable/traditional Hide(DrillDown OK) to show/hide the groups.

I've been in e-mail contact with BO and (as the abbreviation suggests) they stink [thumbsdown]. They keep asking me for the same information over and over again.

I'm going [mad] !!!!!!!!





Bigal (MIS)
Virgin Retail
 
Upvote 0 Downvote
Hi bzzyplaying,

Just had another look at the groupings and sub-reports and noticed that the level that bombs the report out hasn't got a sub-report !!!!

Group 1 - Sub report
Group 2 - Sub report
Group 3 - NO Sub report

Now I am confused !!!!!

Bigal (MIS)
Virgin Retail
 
Upvote 0 Downvote
Hi All,

I've managed to sort the problem out !!

I simply changed the viewer to the Advance DHTML one and all the reports now drill down all the way with no errors.

Still don't understand why the other viewer options caused the errors and BO have not been very forthcoming with any sort of constructive information, so I'm sticking with the Advanced one and I'm not letting anyone breath near the server just incase it decides to stop working !!!!!

Thanks to all who tried to help

Bigal (MIS)
Virgin Retail
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

BeeBear2
  • Locked
  • Question
CE10 Report missing data when ran as a Tab Seperated Values format
Replies
0
Views
62
BeeBear2
BeeBear2
nmee
  • Locked
  • Question
CE10 CMS hangs on &quot;Starting&quot;
Replies
1
Views
97
nmee
nmee
amboswell
  • Locked
  • Question
Why No Add Command Button
Replies
5
Views
110
hilfy
hilfy
bustell
  • Locked
  • Question
CE10 - Disabled User Counting Against License Count
Replies
0
Views
46
bustell
bustell
mamorgan1
  • Locked
  • Question
All Destinations tabs are disabled in CE10
Replies
4
Views
70
hilfy
hilfy

Part and Inventory Search

Sponsor

Back
Top