Hi everyone,
I'm hoping this is a simple case of me over-thinking things!
I have a single constituency that indicates when someone does not qualify for a particular offer that we have available. I have 4 dynamic lists of people that should have this constituency applied and the end date of the constituency is determined by which list the customer belongs to. Easy so far, right?
The trouble is that it's possible for customers to move from one list to another depending on their future purchase behaviour. If I'm using the Manage Constituency utility I can't seem to update the end date of the constituency when people move to a different list.
If I use the Add to List action parameter it will maintain the original end date they had from their original list.If I use the Update List action parameter it will change the end date as desired but any brand new people on the list will not have the constituency added if it wasn't already there.If I use the Deactivate All, Add to List action parameter it will deactivate the constituencies for people on the other lists.
I feel like I need an additional parameter that is a combination of Add to List and Update List.
Has anyone managed to do something similar using the Manage Constituency utility or do I need to start looking at doing this using a SQL Job? I'd prefer the client approach so that it's easy for a non-technical person to manage this going forward year to year but if it needs to be a back end thing then so be it.
Thanks in advance for any advice you may have!
Beth
Two options I can think of off the top of my head:
1. Run the Manage Constituency utility twice for each list -- once using Add and once using Update.
2. When running the utility for the first list, use Deactivate/Add, and then use Add for the three subsequent lists.
If constituents can be a member of more than one list at once, that would complicate things, but it doesn't sound like that's the case. Hope this helps!
Oh interesting! I was thinking along the lines of your first suggestion but got hung up on the idea that I would need two lists (one for ones to be added and one for ones to be updated). That idea wasn't working out well. :)
But I think your first suggestion might be exactly what i need. Back to the testing grind I go!
Thanks!