04-27-2014 05:15 PM
This is my first post to the forums and I want to thank anybody who helps in advance.
We have the SalesLogix DB on the same server as my Accounting software's DB. I have created hundreds of reports on the accounting side using SQL Server Reporting Services. Many of those reports use parameter values and I've never had any problem with them. I've not learned Crystal Reports yet to be able to call data from the accounting system AND SalesLogix at the same time and, honestly, I have a lot of data cleanup to do that I just want to use Reporting Services to reveal before I take the time to learn Crystal.
So, here's my specific problem. I have a report I'm trying to build that uses this simple query:
Select type, account, region, industry, territory
Where (Territory = @EnterTerritory)
When I run that report in reporting services I get this error:
I've been all over the web trying to figure out how to declare a scalar variable in this instance -- everything is so complicated and just doesn't seem to apply. I found some basic reference in one book but nothing I try works.
Any help with be GREATLY appreciated.
04-28-2014 08:49 AM
My problem seems to have been resolved. I found some reference to OLE DB connections not working with SSRS and causing the requirement for Declaring the Scalar Variable.
In futzing around, I went into Reporting Services and changed the authentication type to Windows Integrated -- which broke all of my existing reports. So I changed it back then restarted all the SQL Server services on the server, and voila! no more error message. Makes no sense to me but at least I'm off on my merry way.
04-28-2014 09:40 AM
FYI - I have a customer who uses SSRS for ALL their Saleslogix reporting and does not use Crystal at all.
They also have TaskCentre w/the SSRS tool that makes integrating it (SSRS) w/Saleslogix (or ANY other db source) very easy ;-)
04-28-2014 02:44 PM - edited 04-28-2014 02:44 PM
If you would like a demo and/or talk w/my customer who is doing this.. just contact me directly (info in my signature below)..