• Replies 30 replies
  • Subscribers 340 subscribers
  • Views 505 views
  • Users 0 members are here
Related

LP_VALIDATE_CUST_MERGE

Harpreet Gangyan
$organization

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

Parents
  • $organization

    We have had a customized LP_Validate_Cust_Merge for quite some time now.

    However, with V12.1 we have started to get an error message every time the RaiseError is called.

    On the client side it looks like this.

    Invalid Entry

    Merge not permitted by LP_VALIDATE_CUST_MERGE.

    Warning: Null value is eliminated by an aggregate of other SET operation.

    Anyone else run into this?

    Anyone else have a quick solution?

     

    Here is the type of code that is throwing the error.

    if ( not (@Ug_contest like 'PlanM%' and @Ug_contest <> 'PlanMgr') and @delete_id_count > 0)

      Begin

         RAISERROR  ('Merge not possible: Only Membership can merge  %s', 16,1,@msg1)

         RETURN

      End

  • $organization in reply to Tom Brown (Past Member)

    Hi Tom,

    Yeah, we ran into that as well. in our case, I think the issue for us was due to the migration to SQL Server 2012 rather than v12.1 specifically, so there is a chance the issue we experienced is different than yours.

    But, here is what I changed our RAISERROR statement to in order to get it to work:

    RAISERROR(@ErrorMessage, 11, 2)

    (@ErrorMessage is a varchar variable that we use to build the error message, which allows us to display multiple validation errors.)

    Thanks,
    David 

Reply
  • $organization in reply to Tom Brown (Past Member)

    Hi Tom,

    Yeah, we ran into that as well. in our case, I think the issue for us was due to the migration to SQL Server 2012 rather than v12.1 specifically, so there is a chance the issue we experienced is different than yours.

    But, here is what I changed our RAISERROR statement to in order to get it to work:

    RAISERROR(@ErrorMessage, 11, 2)

    (@ErrorMessage is a varchar variable that we use to build the error message, which allows us to display multiple validation errors.)

    Thanks,
    David 

Children