Join one to many issue

[CCWeedcontrol]

I have a feature class and a table that I need to join. The table and feature class share a common field, The table will have duplicate Acc (ID's), and the Feature class will have just one Acc (ID's). Both are in the same file geodatabase, both have objectIds. The following doesn't crate the one to many join, what am I missing?

arcpy.env.workspace = "C:/Temp/test.gdb"
fc = "C:/Temp/test.gdb/TaxPs"
sourceTB = "C:/Temp/test.gdb/table"

arcpy.MakeFeatureLayer_management(fc, "TaxPs")

arcpy.AddJoin_management("TaxPs", "Acc", sourceTB, "Acc", "KEEP_COMMON")

arcpy.management.CopyFeatures(fc, os.path.join(arcpy.env.workspace, "Taxps_Joined"))

[CCWeedcontrol]

It is making a duplicate but for example the table will have 4 attributes and the feature class will have one attributes. It it creates a duplicate four times, how can I get it to create new records for keep the attributes from the table?

Table

Table
Acct	Field A
14970201	MH
14970201	SFR
14970201	CON
14970201	RV

Feature class

Acct	FieldA
14970201	MH

After Join.

14970201	MH
14970201	MH
14970201	MH
14970201	MH

[VanessaSimps]

Sounds like you need to check out using a relationship class instead of a join. Relate your table with the many to the feature class with the one. 

[CCWeedcontrol]

When I search for joining one to many, I found that join.management should work, unless it doesn't truly work?

Add Join (Data Management)

[VanessaSimps]

I think it really depends on what you are trying to get as a result and how you want to use the data once it's joined/related. 

once you have the join created, what are your plans? Remember,  join only exists inside a map project. you can't publish out joined data (I am assuming you are in desktop with this, not web AGO/AGE). 

[CCWeedcontrol]

Essentially, I need to create point features for every record in the table, which falls within a parcel. I do have CopyFeatures which is suppose to create the features, from what I have read.

What is happening is that, if I run the stand alone script the join.management works but as mentioned I creates duplicates not all the attributes from the table get transferred after doing a copyfeature.

Upon incorporating the script into a model, the Join management function behaves differently from the standalone script. It fails to establish a one-to-many join as observed in the script.