Doh! Yes, I had the requestor and supplier reversed. I now get all of my company_contact records created.
Thanks Jason. --- In [email protected], "Jason Birch" <[EMAIL PROTECTED]> wrote: > > I think I'm missing something. > > If the company_id is stored in a single column in the contacts table, I don't think that you should have duplicate suppliers; you will only match one company per row. Are you using the contacts table as the requestor and the companies table as the supplier? > > If there are duplicates (I could use some clarification on why) you could try specifying a list, and then using a ListExploder to get individual records. > > One thing to be careful of is which attributes you're dealing with. I often use the AttributeKeeper and AttributePrefixer transformers prior to using a FeatureMerger so that there is no room for confusion. > > Jason > > ________________________________ > > From: [email protected] on behalf of wallace_tobin > Subject: [fme] Re: Builiding intermediate tables while converting parent tables in many-to-many > > > > As for the company contacts intermediate table I did use the feature > merger in exactly the way you have mentioned here and I am not able > top get the duplicate contactid_companyid records from the feature > merger even though I have turned on the option to process the > duplicates. The duplicates are created but they do not contain the > information from the company table record as I believe it should. I > can't seem to find a way to get it to give back the duplicates with > the valid companyid? I haven't used the feature merger before so > maybe I need a little direction on getting this to work properly? > Join us at the FME Worldwide User Conference Sept. 21-22, 2006 Vancouver BC Canada. For more information, visit www.safe.com/2006uc. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
