You've got the situation backwards. We want to push fields that are NOT $NULL$ on the staging form; i.e. have data on the import. We don't care if there is data in the existing people record. We want to make sure, however, that we don't overwrite existing data with a $NULL$ such as clearing out an existing email address.
More Background: Some people records may be created by hand, say support users, and have an email address. The imported data may contain that person's information but without an email address. Pushing a null email address to a support user who has a notification method of "email" causes a warning that is enough to stop that record from importing. Yes, I know this can lead to issues where data legitimately disappears and is set to $NULL$ on purpose. There probably isn't a panacea for this. And we probably have to push all the fields because we never know what might change if all those fields are "in play". J.T. Shyman Column Technologies -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eli Schilling Sent: Monday, December 10, 2007 1:11 PM To: arslist@ARSLIST.ORG Subject: Re: Push fields only if not $NULL$ J.T. Why would you only push to fields that are NULL? What if your source has updated since the record was created in the staging form...wouldn't you want the updated value? Would it be easier to define certain fields that you did NOT want to update if there was a pre-existing value. You'd still need to have a filter (or action) for each field...but this would trim the number down from 82. If you wanted to do something for all 82 fields you might be able to get creative with a SQL set fields statement. I couldn't come up with it off the top of my head but you might be able to identify the empty columns that way... Just a few ideas.... Cheers! Eli ________________________________ From: Action Request System discussion list(ARSList) on behalf of J.T. Shyman Sent: Mon 12/10/2007 10:01 AM To: arslist@ARSLIST.ORG Subject: Push fields only if not $NULL$ ARS 7.0.1 We have a staging form with People information. We are performing a check to see if a user matching the staged data already exists. If so, we want to push only the fields on the staging form that are not $NULL$. My thought is to do this with a filter guide and a separate filter for each field...but there are 82 of them. That's a lot of workflow. Is there another way to do this? J.T. Shyman Remedy Consultant Column Technologies [EMAIL PROTECTED] AIM: JToddShyman Y!IM: MCIQuincy ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
