I have a file exported from SFDC that has Contact & Application data. Now I need to bounce it against Contact object to determine which of these records does, or does not have, 1 other Contact field populated.
MATCH (which seems logical choice) found the rows but then didn't bring back any data for the field in question in the Preview. And I know that is wrong. At least 2 records have data in the field in question. But preview didn't show it. So did Match fail because condition I set for that field was where Field value = (nothing) no null to select just left the box empty for the value I wanted to see. Basically hunting down records MISSING data in a key field.
OR is this actually a job for Import or Export to get to the analysis result? To take a file and bounce it against Contact and show where 1 field does or does not have data in it. The use of Import & Export is still confusing. I'm not actually doing either of those things, just want to feed DT a file and pull more data to go with the rows on the file. But maybe DT would consider this as an "import" of a file to look at" Or maybe DT would consider that what I want is an "export" of more robust list of my original fields, plus the data I asked for?
In the past this would have been a quick MassEffect bounce purely for analysis and export but not execution to update anything thru DT, but still get confused by the V5 interface. I can provide screen shots of the MATCH Scenario I saved, but only directly to a Validity Tech, not in open chat. Any advice appreciated! LizK
@LizK - Happy to help! What ultimately is your end goal in this scenario? Analysis or filling in gaps? Am I understanding that you are trying to match the application to it's appropriate contact and push over missing information to the details of the application?
Hi Pugs! Analysis is the goal. Trying to hunt down the situations where data is missing in a particular field. But it has to be only for situations on a given list. So for a given list, when bounced against Contact object, by ContactID, then want DT bring back records where a contact field is empty (null, blank, whatever you want to call that). For some of the records on the bounce list, the field will have data. But in some instances, that field will not. If thru analysis I can identify the records where that field is emtpy, then I can go elsewhere to hunt down the missing data and enter it manually onto those records. This is a corner case audit scenario situation. Hope this makes sense, but if not, feel free to ask additional clarifying questions. Tks! Lizk
@LizK - I am having a hard time visualizing the situation and don't want to steer you down the wrong path. Shooting you an email now so we can setup a call to discuss further, thanks!
