topic Re: A tool that fully combines two attribute tables with keeping the unmatched records, in Data Management Questions

A tool that fully combines two attribute tables with keeping the unmatched records,

JamalNUMAN — Fri, 13 Nov 2015 15:03:21 GMT

A tool that fully combines two attribute tables with keeping the unmatched records,

In the screenshot below, I wanted to combine V1 and V3 tables based on V1 and V3 fields and to have the result as shown in the excel file (in the same screenshot).

How this might be performed?

Thank you

Best

Jamal

Re: A tool that fully combines two attribute tables with keeping the unmatched records,

JamalNUMAN — Mon, 16 Nov 2015 08:04:40 GMT

I got that this tool is available in the FME “FeatureMerger”

Re: A tool that fully combines two attribute tables with keeping the unmatched records,

DanPatterson_Retired — Mon, 16 Nov 2015 09:18:42 GMT

from here Joining attributes in one table to another—Help | ArcGIS for Desktop

this is the default behaviour

When joining tables, the default option is to keep all records. If a record in the target table doesn't have a match in the join table, that record is given null values for all the fields being appended into the target table from the join table.

whether using the Add Join tool in

DesktopAdd Join—Help | ArcGIS for Desktop

Pro Add Join—Data Management toolbox | ArcGIS for Desktop

so if the join doesn't work one way, switch the direction of the join. If you don't like it that way, save the joined file as a separate file and join it back to the file you want the join to go to.

PS moved to Managing Data space

Re: A tool that fully combines two attribute tables with keeping the unmatched records,

JamalNUMAN — Mon, 16 Nov 2015 09:28:22 GMT

Thanks Dan,

I’m aware of using multiple tools to do this sort of work. However, my intent is to find one single tool that can do the job.

Re: A tool that fully combines two attribute tables with keeping the unmatched records,

DanPatterson_Retired — Mon, 16 Nov 2015 09:41:56 GMT

There isn't one, just the join and the results are directional, and you would have to create a model (or a script) to emulate the workflow that I suggest should the intended results not be to your satisfaction or expectations.