Civil3D: Extended pset names overriden while receiving data from Speckle

bekraft commented 1 month ago

Property set names are not handled correctly while sending and receiving data to/from Speckle. They are sent as internal names and replaced by generic Speckle names on load from Speckle.

To achieve a cross tool communication we need stable and correct pset names.

Prerequisites

[x] I read the contribution guidelines
[x] I checked the documentation and found no answer.
[x] I checked existing issues and found no similar issue.
[x] I checked the community forum for related discussions and found no answer.
[x] I'm reporting the issue to the correct repository (see also speckle-server, speckle-sharp, specklepy, speckle-docs, and others)

What package are you referring to?

Civil3D Connector Plugin (tested version 2022)

Describe the bug

PSet names of extended properties are not submitted correctly while sending using internal names since 2.20.wip
PSet reflection and names are not handled correclty while receiving (pset names are replaced by generic Speckle names) since 2.19.3 at least.

To Reproduce

Define a custom extended property set in civil 3d.
Send the object to Speckle.
Receive the object from Speckle.

Expected behavior

Extended property sets are reassembled correcly after receiving data from Speckle. PSet names are taken as key names to properly reference property data from Speckle.