LP_VALIDATE_CUST_MERGE

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
  • 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

  • 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 

  • An update: I just discovered today that our RAISERROR in lp_validate_cust_merge is no longer showing up in the client - we're using Tessitura 12.1.2. The procedure prevents the merge from being scheduled, but the error message isn't displaying. I can run the procedure in SSMS and the error shows up properly there. I'm opening a TASK ticket on that. I'd be curious to know if anyone else is experiencing that.

    Thanks,
    David 

  • Ugh, you can disregard that. I discovered it wasn't an issue with RAISERROR. That is working properly. Sorry for the false alarm!

  • We did experience that here, until we modified the LP_ stored procedure raiserror code as per my post above.

Reply Children
No Data