Unexpected/unwanted type update in case of 2 types with same name

[pawelbaran]

Description:

When updating elements via Revit adapter, type can be changed unexpectedly in case of multiple families containing types with name matching the type name of the updated element. That happens because on push/update Revit adapter attempts to update the type, and the default type picking mechanism is based on name of the property (the object returned by GetRevitElementType method), where the adapter picks first type that matches it.

I scratched my head a bit around that one, looks like the best solution will be adding family name prefix to the type name in name of the property on pull, i.e. after pulling, object returned by GetRevitElementType should have Name in the following format: {familyName}: {typeName} rather than {typeName} - that would eliminate the ambiguity.

Test files:

On SharePoint