HI,
We are looking into customizing this procedure to avoid merging of records are not duplicates. Can somebody shed some light on where this procedure is placed (called within another procedure or something) within Tessitura. This will give us understanding of effects of this procedure run. Thanks for your time and help.
Cheers
Harpreet
Steve,
If you want to check the usergroup of a current user in T-SQL prior to executing some code, you can do something like this:
Declare @usergroup char(8) -- will hold current usergroup
Select @usergroup = dbo.FS_GET_PARAM_FROM_APPNAME('UG') -- this scalar function gets the current usergroup id
If @usergroup NOT in ('ADMIN','DEV') -- Any usergroup ids that you want to allow from T_METUSERGROUP
Begin
Raiserror('Go directly to Jail, do not collect 200', 11, 2) -- Raises an error which prevents the merge from happening
End
Print 'The if statement above blocks users outside of the Admin and Dev groups from getting to this statement'
Hope that helps!
-Ryan
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Steve Carlock Sent: Thursday, May 13, 2010 12:16 PM To: Ryan Creps Subject: RE: [Tessitura Technical Forum] LP_VALIDATE_CUST_MERGE
Ken,
Would you be willing to post the code that you have in LP_VALIDATE_CUST_MERGE that does the override check? I love that concept and want to steal it for use here.
Thanks.
-steve
Information Technology Manager
The Granada
(805) 899-3000 x 111 (phone)
(805) 899-3081 (fax)
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ken McSwain Sent: Wednesday, May 12, 2010 10:06 PM To: Steve Carlock Subject: RE: [Tessitura Technical Forum] LP_VALIDATE_CUST_MERGE
Hi Harpreet
do you think when we click on schedule button some procedure runs and LP_VALIDATE_CUST_MERGE gets called within that procedure.
Yes. That's what happens.
is there any quick override option.
No - there's no built-in override option. We added some code into our version of the script so that members of a particular user group can override it. Only consortium administrators have access to that group - if anybody needs to run a non-conforming merge, they ask us, we review the merge and if necessary check with other consortium members, then log on with that user group and schedule it manually.
Ken
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Hi Steve
Our script is pretty much as Ryan describes it.
I've parked a copy of the full thing in my files here, but this is the relevant bit:--------------
declare @current_ug varchar(8)--get the current ug, to enable bypassing of rules by specific user groups if needed-- set @current_ug = dbo.fs_get_param_from_appname('ug')
--- then we do the void merge check and any other un-overrideable checks first, and then wrap the whole checking process inside a conditional process.;
if @current_ug <> 'AdMerge'begin --1-- the merge validation rules
end
---------------------------------
The "AdMerge" user group is a special group used for only this purpose. If we want to override the merge validation, we have to re-login using this group, and it has no permissions to do anything else, so we have to get out again to continue working. That's to make sure that every use of this power is deliberate - we don't want admins accidentally putting a non-conforming merge into the schedule.