Beginning with the Bentley Map V8i (SELECTseries 3) release, the referential integrity of XFM feature instances (graphic and non-graphic elements) is protected when design files are opened in a pure MicroStation session. This additional level of data protection was implemented after careful consideration of several technical support incidents where customers edited their Bentley Map produced data in other products (e.g. MicroStation) without Bentley Map present, resulting in unexpected data corruption.
Example of reported design file editing workflows and resulting data problems included:
As a result, if Bentley Map is not use to edit the design file, XFM feature instances cannot be manipulated to:
The Bentley Map product team is working to gather functional requirements from numerous customers who have existing workflows that require "limited" editing or manipulation of Bentley Map data in scenarios where Bentley Map is not present. The objective of this effort is to expand what type of editing or manipulation can be done of data when Bentley Map is not present, while at the same time preserving the data integrity.
Sebastian, Dan thank you for the response. I will have a look at the update (bentley-map-v8i-selectseries-4-08-11-09-666-update-2) first.
Sebastien's link shows some of the work that has been done in this area since Export command was introduced in the Bentley Map V8i (SELECTseries 3) 08.11.09.91 release in 2012. Refer to the product README file's "What's New or Revised" section to see new functionality or improvements to Released products. The software Fulfillment Center provides that link.
Also, this communities' Announcements Forum includes the Release Versions, and a link to current corrections to reported defects: communities.bentley.com/.../114440
Dan, is there still no solution for transferring Bentley Map data to Microstation? We have the same problem as AlanH, it really affects productivity.
I can understand the reasons why native features were created and that part of the process makes total sense to me. However, in the nicest possible way, surely Bentley can walk and chew gum at the same time. By this I mean, surely you can resolve the Map issue while still maintaining easy compatability with your core Microstation product.
I think one of the big strengths of Bentley Software is its compatability between applications. What was done here, IMHO as a user was real 'silo' development which concerns me more than the individual problem. We have a problem with Map, lets get a quick solution and whether it causes a problem in Microstation, well that's something that will get resolved in a year .........or more.
For Sites that use Map and Microstation this inability to be able to easily copy map feature through into Microstation is a real and basic flaw that causes productivity issues. For such a big break in compatability, all that was really needed was for Microstation to automatically strip the enhanced element types off if elements were copied from Map to Microstation.
At our site we use Map and Microstation and we need to be able to interchange easiliy. Because we weren't aware such a big break was coming, by the time we actually log the issue, discuss it with Bentley and get some indication a solution will be found years will go by. This is far to long.