Missing attributes in Shp export

Thanks Jeff, this works. If I do this I can see that there are 2 elements on my polygon-layer that are excluded by the filter and then I can export the new level ok.

In this case I am working in a file with only one level but I regularly have to assist customers that are having shp-export problems that are working with 20-30 levels in one file and if the export process fails there is no indication (well there is the element id but it's tricky to track down) of what elements are failing. I have experienced  that Bentley Map is strict on that my data is clean and if I for instant have lines or text on a point level  the export process stops.

Is it not possible in future versions to have the option of just skipping over problems like these and complete the export ?

Karl,

I have this problem experienced before, you need to re-evaluate your data if your data has no error, meaning using Data Browser review your attributes using fence or view. If your data have errors you cannot export your data into shp file. Correcting the errors is your passport to export your data correctly.

Hope this helps,

Jun

Karl,

You should be able to use the "Change Attributes" command along with a "Fence Filter" to move your elements to a new level. For example...

1. Make a copy of your design file for backup purposes until you have validated the changes.
2. Open your design file and create a new level (e.g. MyNewLevel).
3. Place a fence around all of the elements in your design file, keeping in mind that the "Fence Filter" will control which elements participate in the upcoming "Change Attributes" command.
4. Define an active "Fence Filter" using a SQL statement which selects all database rows linked to your elements (e.g. DS=SELECT * FROM MYTABLE).
5. Activate the "Change Attributes" command and select the "Use Fence" and "Level" options, selecting your previously created level (e.g. MyNewLevel).
6. Press a datapoint to accept and begin fence processing.
7. Deactivate your "Fence Filter" using a "DS=NONE" keyin.
8. Exit your session.
9. Start a new Bentley Map session.
10. Verify that your elements have been properly moved to their new level.
11. Open the "Interoperability" application and export your data.

Hi Jeff, this might be the problem. If I create a new level and move some of my polygons to it then I can export that level ok. The Masking tool show me no "no database" elements but I can see there are more elements on my problem level than the number of vsql review responds. The DBCHECK command tells me all is ok. What would be helpfull in this case would be the possibility to select and move to another level the vsql review results. That possibility used to be in the vsql dialog (and hilight) but it's looks like it's bin removed in BM or do you know of a way to do this ?

regards

karl

Karl,

It sounds as if the Dynamic Feature Scoring (DFS) may be finding at least one feature occurence in your design file which has no RDBMS linkages before all of the other occurances with the linkages. When this happens, the inferred feature class definition will not have any business properties. Attempts to use the "Data Browser" or "Interoperability > Preview" functions which result in no apparent business properties are usually a good indication that the inferred feature class is using a simple MicroStation element with no RDBMS linkages etc...

Do you possibly have any elements w/o RDBMS linkages that are on the same level as those which have your valid RDBMS linkages? In the "Utilities" tool palette of Bentley Map, the "Masking" tool has display modes which can help you visualize elements with and w/o RDBMS linkages. After removing (or moving to another level) those elements which have no RDBMS linkages and restarting a new Bentley Map session, your data should show business properties and export as expected.