Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Monday, November 25, 2024 
 
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!
 Reporting & Notification Forums - Reporting
Forum to discuss reports for SalesLogix including Crystal, SQL Reports, etc. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to Reporting | New ThreadView:  Search:  
 Author  Thread: Crystal Reports - can't use "row_number" via Command through OLEDB
Sean
Posts: 2
 
Crystal Reports - can't use "row_number" via Command through OLEDBYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 05 Oct 11 11:14 AM
fiogf49gjkf0d

Hi,


I'm trying to pass the following through the Saleslogix OLEDB connection to generate a rank column, however it fails everytime:


"row_number() over(Partition by "acc_code" order by Sum("Sales") DESC )"


If I run it through ODBC, it works fine - but I can't then distribute the report via Saleslogix.


Does anyone know why this won't work or how I can fix it?


 


Thanks

[Reply][Quote]
Raul A. Chavez
Posts: 1300
Top 10 forum poster: 1300 posts
 
Re: Crystal Reports - can't use "row_number" via Command through OLEDBYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 06 Oct 11 9:39 AM
fiogf49gjkf0d

The obvious answer to why this doesn't work through SalesLogix is that the SLX OLEDB Provider doesn't like it.


As far as a workaround, you could try wrapping the Query on an SQL View (if possible) and then enable that view within SLX. That would allow you to use the View on the Report, and have the view invoke your code.


Now, I mentioned "if possible" on using a View. As is, views don't support the ORDER statement (on most cases). Never the less, this is a typical workaround to try and bypass issues with the Provider.


 


Another method is to execute a Script before Opening a Report. This would allow you to execute the Query, write the Data to a "Reporting Table" which would be what you use within the Report to display the data.


Off course, since the issue is the provider, you may still need to execute your query via a direct SQL Connection to bypass the SLX OLEDB provider.

[Reply][Quote]
 Page 1 of 1 
  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!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 11/25/2024 12:42:56 AM