XLCubed XL3ExecuteSQLProc error

First of al this is a RTFM if you know where to look ;-).


Consider the following (simplified) procedure)


CREATE PROCEDURE uspGetNewId
@UserName varchar(250)
AS
BEGIN--
-- Some more magic
--
SELECT NEWID() INTO TBL_LOG
END


If you add =XL3RunSqlProc(B1,1,"uspGetNewId",XL3UserName()) to your sheet you get the following error:

Procedure or function 'uspGetNewId' expects parameter '@UserName', which was not supplied.
The problem is dat XLCubed access the database with hardcoded parameters: @Parameter1,@Parameter2,@Parameter3....


There are 3 approches for fixing this:
1
Rewrite or wrap your procedure like this, using the default parameters :


ALTER PROCEDURE uspGetNewId

@Parameter1 varchar(250)




AS

BEGIN


 --

-- Some more magic

--

SELECT NEWID() INTO TBL_LOG




END





2
Use XL3RunSQL instead and compose your own SQL string:
=XL3RunSql(B2,1,"EXEC dbo.uspGetNewId @UserName='"&XL3UserName() &"'")


3
Add a dedicated ODBC connection (see manual)


Till Next Time

Comments

Post a Comment

Popular posts from this blog

XL3SetProperty Connection

Image
With V9.1 we can dynamically change a connection during runtime , using XL3SetProperty. The general statement looks like this: =XL3SetProperty("connection","<<NumberOfTheBaseConnection>>","copy",   “<<numberOfTheAlternativeConnection”) To get this to work you need at least 3 connections to your source 1 = Connection to your base source (This will be your “working” connection) 2 = Connection to your alternative source 3 = Connection to your base source   (You need this to be able to switch back to your base source) In this example we are using 1 as working , 5 as alternative and 6 as base source. Add a slicer to your report which fills a cell with the connection you want to use: Add a cell with the following formula: Be sure to have your working connection between quotes! And the cell properties of B1 should be set to “text”. Till Next Time
Read more

XLCubed to which Cube or Database is a report connecting?

Image
We are planning a major overhaul on one of our cubes. The problem is that we don't know which reports are connection to this cube. We have over twohunderd possible candidates and don't want to open each one to check. I wrote a simple query to extract the connections from the repository: SELECT DISTINCT   fp.cPath as ReportPath , r.[cName] as ReportName , case when CHARINDEX('<connections>',convert(varchar(max),f.oData)) > 0 THEN SUBSTRING(convert(varchar(max),f.oData), CHARINDEX('<connections>',convert(varchar(max),f.oData)), CHARINDEX('</connections>',convert(varchar(max),f.oData)) - CHARINDEX('<connections>',convert(varchar(max),f.oData))+14) END as CubeConnections , case when CHARINDEX('<sqlconnections>',convert(varchar(max),f.oData)) >0 THEN SUBSTRING(convert(varchar(max),f.oData), CHARINDEX('<sqlconnections>',convert(varchar(max),...
Read more