OK, the client was monitoring this discussion with great enthusiasm hoping for a solution. You are correct, the group of records that needs an Action will indeed be different every time.
For example: they are event attendees who have made a payment on a certain day. Let's say 100 people came to an event on 11/1/2001. I can generate a group from Payments, now I want to give them all an Action that they attended Event X, so in the future we can look people up by their event attendance (or whatever other Action) and not guess from their Payments records. I really do want to do the same exact thing for Actions as is available for Contacts. How difficult would it be to copy and modify the script? Thank you! Melinda Conness Minnesota NARAL 550 Rice Street Saint Paul, MN 55103 (651) 602-7655 [EMAIL PROTECTED] -----Original Message----- From: Barry Madore [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 2:02 PM To: TechRocks Support Subject: [support] Re: Batch Actions data entry Good point, Carl. I will need to ask the client how they do this currently (create/query the found set for batch entry). You are correct, I believe, in the assumption that it will not be the same group each time. In my haste to think about the script alteration process, I did not think to inquire about this part of the equation. Perhaps they are monitoring this discussion and can weigh in on this. -barry -- Barry Madore Technology & Web Development Specialist MAP for Nonprofits Direct: 651/632-7235 MAP: 651/647-1216 email: [EMAIL PROTECTED] MAP web: http://www.mapnp.org > From: Carl Paulsen <[EMAIL PROTECTED]> > Organization: New Hampshire Rivers Council > Reply-To: "TechRocks Support" <[EMAIL PROTECTED]> > Date: Mon, 14 Jan 2002 12:37:57 -0500 > To: "TechRocks Support" <[EMAIL PROTECTED]> > Subject: [support] Re: Batch Actions data entry > > Although I haven't done this, you could use the batch process scripts > for a similar process for entering Actions. This process isn't real > tricky. It would take some work to do this but at least you'd have a > model for one way to do it. In my view, the real trick would be to find > a way to quickly and easily create the found set you want to batch > process. I presume your batch will never be the same set of records or > that you'll never be able to anticipate (with some kind of record flag) > who will need to be processed this way. How do you query for a set of > records whose only commonality may be that they are a subset of the > original contact? > > Carl ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org --------------------------------------------------------------------- ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
