Thanks for reporting this, and I’m really sorry that you’re experiencing such a disproportionate number of problems.
It seems that this stored procedure is mistakenly required – this was part of a security layer to avoid using this Functoid to bypass SmartsIntegrator security on SmartsIntegrator databases, and clearly we must have been doing this in our testing.
The attached update corrects this, and this will also be in version 1.3.021. Alternatively as a temporary measure you can define the following stored procedure in your database :
CREATE PROCEDURE [dbo].[WTSP_GetSecurityGroups]
AS
BEGIN
SELECT ’Dummy ’ AS SecurityKey, ’ ’ AS SecurityValue --Make sure these are standard quotes
END
Thanks,
Ben.
PortedQuery : I'm attempting to utilize the database functoid in a map, and am getting the following exception: Could not find stored procedure 'WTSP_GetSecurityGroups'.
Is that something I need to setup?
Ben Jackson
SmartsIntegrator Technical Support