Hi folks,
I'm about to write a custom view for use in Mail2 and, rather than starting from scratch, I was wondering if anyone else had one they'd share or have some pointers as to best practice.
I'm in a consortium environment and am aware that I'm going to have to make adjustments to ensure I adhere to our data mining policy (by using local, secure views) and would appreciate hint/tips/tricks from anyone else using custom views.
Thanks!
Martin
Hi, Martin. I guess it really depends what sort of view you need. I made a few views for automatic performance reminders. If the code for those would be at all helpful, I'm happy to share.
The weirdest thing I found in setting up Mail2 custom views was that I had to set up so many with different conditions, rather than just putting fields that would flag certain things. Like I couldn't make one view that had a subscriber Y/N field, I had to make a view that returned subscribers and a separate view that returned nonsubscribers, because according to our marketing guy who was setting up the automatic emails, he could not use such a Y/N field to limit which people were returned.
Another weird thing is that Mail2 can't handle any fields being NULL, and if I returned a blank string or a 0 it messed up formatting, so we finally had to use ' ' as the isnull default value.
A third weird thing is that the performance date it was going to select on had to be named custom_date.
Hi Andrea,
Thanks for this information - If you were happy to share your custom view script I'd be very grateful to receive it!