Pesky Prevailing Procedures

I understand that the Suggested Contribution box on the Subscription Summary screen gets populated by LP_GET_CONTRI1.  Until we decide how we want to calculate that amount for the people that aren't represented in T_CUSTOM_ASK_AMOUNTS, how would we keep that code from running and populating that field with the stock formulaic amounts it does?

Is it as simple (and unsophisticated) as modifying the stored procedure to comment out all of the code, or can we simply shut off the automatic triggering of that stored procedure until we see fit to revisit it?

Thanks, Tessiturians!

Parents
  • Former Member
    Former Member $organization

    Matt,

    My preference would be to comment out the code in the local procedure. Since the LP_ is called by a Tess standard stored procedure, I'd want to keep my hands off that.  Also (particularly in a consortium environment) it's possible that there may be more than one season or set of users who need to run something through the process.  So commenting out the section in the local procedure that deals with the specific season's suggestions makes the most sense to me.

     

    - Levi

Reply
  • Former Member
    Former Member $organization

    Matt,

    My preference would be to comment out the code in the local procedure. Since the LP_ is called by a Tess standard stored procedure, I'd want to keep my hands off that.  Also (particularly in a consortium environment) it's possible that there may be more than one season or set of users who need to run something through the process.  So commenting out the section in the local procedure that deals with the specific season's suggestions makes the most sense to me.

     

    - Levi

Children
No Data