We did check and we did keep the Execute SQL set to false. There were actually 2 different problems that we were dealing with. 1 was related to problems with the new beta templates accurately executing this custom stored procedure:
Create Procedure [dbo].[_UserPermission_AddRemoveCSRole]
(
@Action int=0, -- 0-Add, 1-Remove
@AppUserName nvarchar(256),
@UserRoleName nvarchar(256)
)
As
Declare @AppName nvarchar(256)
Set @AppName='tcanet'
Declare @CurrentUtcTime datetime
Set @CurrentUtcTime = getUtcDate()
Declare @AppUserID uniqueidentifier
Declare @UserExistsReturn int
Declare @UserInRoleReturn int
Exec @UserExistsReturn = dbo.aspnet_Membership_GetUserByName @ApplicationName=@AppName,
@UserName=@AppUserName,
@CurrentTimeUtc=@CurrentUtcTime
Exec @UserInRoleReturn = dbo.aspnet_UsersInRoles_IsUserInRole @ApplicationName=@AppName,
@UserName=@AppUserName,
@RoleName=@UserRoleName
If @UserExistsReturn = 0
If @Action = 0
If @UserInRoleReturn = 0
Exec dbo.aspnet_UsersInRoles_AddUsersToRoles @ApplicationName=@AppName,
@RoleNames=@UserRoleName,
@UserNames=@AppUserName,
@CurrentTimeUtc=@CurrentUtcTime
Else
Return -2 -- Cannot add - User already added to the role
Else
If @UserInRoleReturn = 1
Exec dbo.aspnet_UsersInRoles_RemoveUsersFromRoles @ApplicationName=@AppName,
@UserNames=@AppUserName,
@RoleNames=@UserRoleName
Else
Return -3 -- Cannot remove - User is not added to the role
Else
Return -1 -- Invalid User
Return 0
GO
The other was that no custom stored procedures that returned views would work. As mentioned in the previous link, they were all missing from the embedded xml file. I'm curious if you can do a test with your setup to see if you can create a custom stored procedure that returns a view.