7/9/2025 5:35:11 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss general administration topics for SalesLogix (including LAN & remote topics). View the code of conduct for posting guidelines.
|
|
|
|
Problem in Report Generation after SLX version upgradation
Posted: 30 Jul 07 3:08 AM
|
Hi,
We've recently had a version upgradation from v5.2.x to v6.2.6.
Some of the crystal reports are causing some trouble now.
One of them, when opened in client does not respond, but if the same is opened in Architect it opens up.
Are we missing on something...i mean do we need to do something to make the reports compatible with the latest version?
Can anyone provide any pointers?
TIA.
Richa |
|
|
|
Re: Problem in Report Generation after SLX version upgradation
Posted: 30 Jul 07 7:39 AM
|
There are steps listed in the V5.2 to V6.2 workplan that detail the steps that are needed to convert a V5.2 report for use in the V6.2 environments. The upgrade should take care of the baseline SalesLogix reports, however, you will need to take care of any reports you created.
Did you perform these steps on the reports that are giving you trouble? |
|
|
|
Re: Problem in Report Generation after SLX version upgradation
Posted: 01 Aug 07 12:40 AM
|
Hi Frank,
As you say, I'm sure the team would have followed the steps that are needed to convert a V5.2 report for use in the V6.2 environments during upgradation.
But still I would like to check.
I'm trying to download the document from the site but there is some network problem.
Could you pls guide me through the steps..??
TIA.
Richa. |
|
|
|
Re: Problem in Report Generation after SLX version upgradation
Posted: 01 Aug 07 6:38 AM
|
Task 68 and 69 have to do with report conversion.
68 If your company has custom Crystal Reports, convert each report to OLE
DB format to ensure compatibility with v7.0.1.
Task 68 Details
To be compatible with v7.0.1, you must manually convert custom Crystal Reports to the OLE DB
report type. Before converting, save your existing reports to a bundle.
The standard SalesLogix reports have been converted to OLE DB and are included in the Upgrade
Bundle. The list of converted reports is not included in Chapter 5, “Changes to Existing Active
Plugins”. Review the Upgrade bundle to understand which standard reports have been converted.
Note If a Read/Write password is set in the Connection Manager and you create a new Crystal
Report, you will receive an error when attempting to create an OLE DB connection in Crystal. Refer
to SupportOnline/Sage Online Support and Services. Search on article “09170304” for more
information.
Before converting reports, create a Data Link connection to your reports database. This connection
can be used when converting reports to reduce administration time.
To create a Data Link connection .UDL file
1 On the computer where you plan to convert reports, open Notepad.
2 On the File menu, click Save As, and save the file to any location with the extension .udl. For
example, Reports.udl.
3 Browse to and double-click the .udl file.
4 In the Data Link Properties dialog box, create a connection to your SalesLogix database using
the SalesLogix OLE DB Provider.
If necessary, access the Online Help system for assistance.
To convert a Crystal Report
1 In the v7.0.1 Architect > Manage > Reports.
2 Select the report you want to convert, and then click Launch Crystal Report System. When
prompted to check out the report, click Yes.
3 On the Database menu, click Set Datasource Location.
The Set Datasource Location dialog box appears.
4 In the Replace with section of the Set Datasource Location dialog box, expand Create New
Connection, and then double-click OLE DB (ADO).
The OLE DB (ADO) dialog box appears.
5 In the Provider list, select SalesLogix OLE DB Provider.
6 Select the Use Data Link File check box.
7 In the Microsoft Data Link File box, browse to and select the .UDL file you created in the
previous section.
8 Click Next.
9 On the Connection Information screen, type your database Password, and then click Finish.
10 In the Set Datasource Location dialog box Current Data Source section, select your report
database.
11 In the Replace with section, select your OLE DB Provider connection.
12 Click Update.
To verify the report converted properly, open the report in Crystal Reports Preview.
Note If you have any sub-reports within a report, make sure you also update the sub-report
sections.
13 After the conversion, ensure you release all reports to all users and sync all changes to Remote
users and Offices.
69 If necessary, update your custom reports.
Task 69 Details
SalesLogix version 7.0.1 requires Crystal Reports XI. This change may require updates to your
custom reports. SalesLogix recommends you understand what changes may be necessary and
update your reports as appropriate.
Remove or Re-create the “Sample” Reports
Five reports that are referenced by scripts were renamed to remove the word “Sample” from the
name. The old versions of the reports are not removed and continue to appear in the Reports view
along with the new, renamed reports. Do one of the following:
• If you have not customized the old versions of the reports, remove them.
• If you have customized the older versions of the reports, either re-create your customizations in
the new versions, or delete the new versions of the reports and rename your customized reports
to remove the word “Sample” from the names. For information about renaming a report, see the
“Report Properties” topic in the Architect Help.
The following reports have been renamed to remove “Sample” from the name:
• Account:Account Detail
• Contact:Contact Detail
• Opportunity:Forecast by Account Manager
• Opportunity:Opportunity Detail
• Ticket:Support Ticket
Check Report Filters
If your custom report(s) contains filters, make sure the filtering information is set correctly.
To verify report filters
1 Architect > Manage > Reports.
2 Double-click the custom report that contains filters.
3 On the Crystal Reports Properties dialog box General tab, verify the User, Group, and/or Date
filters are enabled as appropriate for the report.
Set Report Parameters
If your custom report(s) currently have parameters set, reset the parameters after upgrading. The
upgrade to Crystal Reports XI removes the default values used by parameters. For example, if you
had a parameter prompting for a Yes/No value, users must choose Yes or No every time they run the
report unless the report has a default value reset for that parameter.
Verify the Released Version
Use the Architect Manage Plugins dialog box to make sure the latest report version is released to
users. There may be multiple versions of the same report in your database. Verify the correct version
is released to the appropriate users. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|