Rhino user attribute to iModel category workflow

[eap23]

Hi,

I am following the Bentley Accredited iTwin Developer--Associate Level course. In the sample MicroStation file House_Model.dgn a new item type SmartDevice was defined:

The property SmartDeviceId is used to link federated data to the actual geometric object.
Following this principle I want to define a similar custom id in a Rhino file. As stated here https://communities.bentley.com/products/digital-twin-cloud-services/itwin-services/w/synchronization-wiki/47595/supported-applications-and-file-formats the Connection Type for "Rhino (.3dm)" files is MicroStation.
What would I have to define in the Rhino file to have it translated to a Category of it's own by the MicroStation connector (similar to DgnCustomItemTypes_HouseSchema.SmartDevice in the sample above)?

[jffmarker]

To help clarify, are you interested in having, for example, Rhino user data get converted to item types by MicroStation, and thus it would then come across to the iModel as an object property? @c-macdonald @mgooding

[jffmarker]

I think ultimately that's going to need enhancements on the Rhino file I/O that MicroStation provides. I'll try to find out how they handle feature requests like this.

[jffmarker]

The MicroStation team recommends requesting Rhino file I/O enhancements on https://microstation.ideas.aha.io/

[eap23]

Thanks for checking with MicroStation team!
Are the original GUIDs from Rhino persisted in the converted iModel?

[eap23]

@jffmarker posted at https://microstation.ideas.aha.io/ideas/MSR-I-680.

[jffmarker]

According to the MicroStation team, the initial DGN conversion does not retain the Rhino IDs, so therefore they cannot be persisted to the iModel either.