Subscription Constituency

Hi Parnell

Depending upon how your organization operates, using the LP_UPDATE_SUB_HIST may not be suitable for adding constituencies. That is, you may need to add this to the procedure if it has been previously modified, or your organization may have multiple seasons in one year that would be using the same constituency and the current procedure doesn’t allow for a season string.

Instead of modifying the procedure, you could use the report Manage Constituencies under Data Management. All you need to do is create a dynamic list that identifies who are to get the constituency (based upon subscription history or other criteria). Once you have set the report up can then schedule it to run on a daily basis.

When you open the parameter window for the report click the Report Help button to get all the information about what each parameter does. I would suggest to trial it in your Test environment first.

Always good to have a 2^nd option!

Sandra

Hi Parnell

Depending upon how your organization operates, using the LP_UPDATE_SUB_HIST may not be suitable for adding constituencies. That is, you may need to add this to the procedure if it has been previously modified, or your organization may have multiple seasons in one year that would be using the same constituency and the current procedure doesn’t allow for a season string.

Instead of modifying the procedure, you could use the report Manage Constituencies under Data Management. All you need to do is create a dynamic list that identifies who are to get the constituency (based upon subscription history or other criteria). Once you have set the report up can then schedule it to run on a daily basis.

When you open the parameter window for the report click the Report Help button to get all the information about what each parameter does. I would suggest to trial it in your Test environment first.

Always good to have a 2^nd option!

Sandra