What is the best way of creating a constituency for those that purchase a subscription ticket?
When some purchases a subscription ticket we need to create a constituency so we are able to pull that information via the WebAPI.
THis would be something that happens regularly
Hi Parnell,
Take a look at the document called Localized Procedures (I've attached it to this post)...there are two procedures which populate Performance and Subscription History...both have optional parameters to add a particular constituency to each customer based on the Subscription/Performance seasons a customer buys...See below for Subscription History blurb from the Localized Procedures document...Hope this helps...Cheers, James
LP_UPDATE_SUB_HIST This procedure is designed to update the subscription history table from live orders containing fixed seat packages. It is not part of the application, and is instead run from the SQL Server Job Scheduler. As such, this procedure can be changed in any way desired, including adding or subtracting parameters. Current parameters to this procedure are season_no and constituency. Constituency is optional and indicates a constituency code which should be applied to all constituents which have subscription history rows added. This procedure, as written, can be run anytime. It deletes all existing subscription history for the season and recreates it, then optionally removes all existing constituencies of the desired type and recreates them.