[BM SS4] What happens to User Data Linkages?

I've got a regular MicroStation drawing with shape elements that include a User Data Linkage that points back to an Oracle table. What happens to that linkage when I open that drawing in Map Enterprise, and use the "Promote" tools to convert that simple shape into a native feature residing in a SQL*Server database? Is it lost? Is there any way to "capture" that linkage? The MSLINK value is the record ID of the Oracle data that I would want to insert into the data columns of the SQL*Server spatial table. We've got many shapes, so I'm hoping there is some automated process that can be set up to "preserve" that linkage information so it can be used to ensure the right record from Oracle is associated with the right record in SQL*Server.

Thanks,

Bruce

  • I will gather the info as soon as I get a chance.

    I've been examining the "results" of the "Promote" tool (Feature is Polygon Collection). I begin with 5 elements selected (4 Complex Shape Inferred Features and 1 Grouped Hole inferred Feature), perform the "Promote" ( New element for each in selection set, do not remove original) and I'm ending up with 4 Inferred Complex Shape Features, 8 Complex Shape Native Features, 5 Polygon Collection Native Features and 1 Grouped Hole. The 8 Complex Shape Native Features must be the initial 5 complex shapes and the 3 "holes" associated with one of those shapes.

    I'm studying the OnValidate() event to try and see if I can correlate what elements are being passed in.
  • OK - I *think* I know what the issue is. My data includes "grouped holes" elements and when that top level element is queried for database links, none are returned (the result from Geometry.GataDatabaseLinks() is empty). Trying to extract a MSLINK from the non-existent database linkage was aborting the execution of the rest of the program. I added in a test to make sure a DatabaseLink array was returned, and things are much better. It seems the linkage I'm looking for is on the "Grouped Hole" element, and not any of the sub-parts, so there are no appropriate database linkages on the "sub-elements". Maybe there is a way to extract them from a Grouped Hole, but I'll have to study that some more.