lost subtype when register feature from file geodatabase

Hello.

For feature "KhuChucNangP", only the "doiTuong" property has a subtype defined. The default subtype defined for "doiTuong" is "Co So An ninh". So, only these subtypes could been seen as domain list for that feature since this is the only define. That is my understanding here. If I am wrong, please be more precise of where you should see other subtype defined. Please let me know if I miss something.


Sebastien Lefrancois [Bentley]

Hi,

Bentley Map does not support second level of Values and Domains for a subtype define in a Esri File Geodatabase.

Let me summarize what you already overserved:

For field "loaiKhuChucNang", the domain "loaiKhuChucNang» is defined in ArcGIS and it is recognized in Geospatial Administrator register feature as a domain list.

For field "doiTuong", no domain is defined in ArcGIS. Subtypes are defined in ArcGIS and the list of Coded Value subtype is recognized in Geospatial Administrator register feature as the "KhuChucNangP_SubType" domain list.

All default values and the related domains list values are not supported here and they won’t be used. Only first level domain list defines and Subtype (converted as Domain list) will migrate to Geospatial Administrator and Bentley Map.

Create values relationship in Bentley Map could be created by using Property watchers. But this could be a complicate job to do by using Esri File Geodatabase Connection. That would require a rebuild of data structure by bring back all second level data to the first level and recognize as ComboBox property in Bentley Map. So, the will required ArcGIS field define as subtype or Domain.

That is a suggested workaround I could see for now. Sorry for the inconvenient.

Regards,

Sebastien Lefrancois [Bentley]

As gentle reminded, here some limitation of Esri file Geodatabase support in Bentley Map:

• Subtypes are supported in that they are registered as a single feature with a domain containing the subtype values. Property based symbology rules can be used to differentiate the subtypes.
• Feature data sets are registered as separate features.
• Domains are supported only as coded value domains.
• Relationships that can be modeled as sub features are supported. However, support is read-only. Features involved in relationships cannot be created, updated, deleted, or exported.
• Annotation sub features are not supported in the Esri file geodatabase due to limitations of the API.