Hi,
I'm looking for some help getting started with building stored procedures for TNEW custom fields vs sending them to CSI.
Having trouble getting started and not finding much documentation on this, I don't know what variables are sent to the procedure from TNEW, like session key, order number, etc.
Like for instance LRP_TNEW_GET_ORDER_CONTRIBUTIONS is a stored procedure that looks up order info, so if I have TNEW run that stored procedure, will it send it the order number?
Anyone have any examples of something simple, like using a stored procedure in a custom from field to update an attribute in a constituent record or something like that?
Thanks in advance for any help!
Mark
Thank you all so much for the info, Martin, I'll be reaching out when I'm back at work Thurs to see if you can send me a copy of the code. All of this is great info for me to get started, I'm not a newbie to SQL or programming in general but just needed some examples to get my head around how it works. Eventually the first thing I'd like to do is the following:
- When someone submits additional names under a new membership purchase via a tnew custom field it triggers a stored procedure that:
- (checks for if the additional name is already connected to the account) - checks if name is already an existing const record - if so...
- If not then adds new constituent record for additional name on membership and connects to the household (via affiliate I believe is how our setup is)
That's the very short of the first programming I'd do - but it just would automatically create a new record and connect to the household constituency vs our membership staff having to do this manually every time someone adds an additional name on 'memberships + additionals' (our memberships are confusing which makes things harder, but just trying to save staff time!!!)
More to come, thanks again!