Sales Order and Qoute History Report

SOLVED

Hello... I'm attempting to duplicate the standard report Sales Order and Quote History Report but changing some of the fields that display. I want to replace Unit of Measure with Prod Line. So created a new Report Setting named PRODUCT LINE.. then remove the unit of measure field from report then added Prod line.. When I do a preview within Crystal the new field shows however when I actually run the report no data displays. So I went back and ran the STANDARD report with same report criteria and it did show data. 

I must have missed a step or two but why does no data display for new report???

Thanks much for any help.. 

Bob 

  • 0

    The reports on the reports menu are based on Crystal works tables that do not exist until the print program is run. If you try to edit the form code and refresh while in the designer no data will appear because the works tables are not populated. You have to save and close and run from the Print panel off the reports menu.  Also how did you add the product line to the report as it is not normally part of the table. The correct way to do it is to create a UDF and add to works table. DO NOT link in tables. 

  • 0 in reply to BigLouie

    Hi BigLouie... I understand that previewing within designer will not produce any data. I had saved in designer then went out to Sales Order Reports menu reran the report but instead of selecting STANDARD I selected the new Report Setting I created named PRODUCT LINE and here no data displayed but the PROD LINE header did displayed.  Its almost seems like the new report is not pointing to the tables correctly.  I'm doing all this within a test company where I had copied the production company into.  

  • 0 in reply to Bob@TED
    verified answer

    Does your report have any tables other than the work table? (Don't do that... add a UDF to the work table instead, like BigLouie advised).

    Did you change the report's data source? (Reports run from within Sage need the report's data source to be configured correctly).

    Both of those things can easily break a report's functionality.

    Are you using SQL / Premium?  Or Standard / Advanced?

  • +1 in reply to Kevin M
    verified answer

    So that was it... I did have the CI_Item table added so I removed it then created the UDF then added it to report and now I see the data on the report.  Thanks for the help gents.. 

  • 0 in reply to Bob@TED

    Sorry about this but I did want to add a question to this post... if I can't I will post another. Now that I have the report working I created in a test company so what is the best way to move what I did to our production company?? 

  • 0 in reply to Bob@TED

    I use Windows Explorer to copy the Crystal Report between company codes manually.

    \MAS90\MAS_###\Reports\##_#####PRINTING\FormCodeName\TheReport.rpt

  • 0 in reply to Bob@TED

    When you create a report the system makes a folder in the Reports folder under the company code. So if you look as MAS_XXX where XXX is the company code you will see a folder called Reports and inside of that you will see a folder called SO_SalesOrderandquoteHistory.  Inside of that you will see the report.  In live company create a new report and make a slight change so the system will create the folder. Then just copy from the test company to live company folder and over write the one you made the slight change to.

  • 0 in reply to BigLouie

    Ok.. I did what you suggested and I do get the correct report however I notice when I select Database Expert in field explorer within Crystal it prompts me for username/pw which is fine but I notice the data source is the test company not the production company... does that matter now that the report is in the production company. 

  • 0 in reply to Bob@TED

    Nope. If you run from reports menu it will use same company you are in.  

  • 0 in reply to Bob@TED

    If you use a named DSN (other than SOTAMAS90), it won't work, but that is easy enough to test.

    If you are on Premium / SQL, the fix is a bit more complicated...