Thank you for your questions Rajendra. These are age-old issues encountered where GIS meets Cartography. For simple Mapping and GIS needs, try to limit the amount of points, segments, and detail when you place the features. Take care to design your Features…

Krister, The ability to use expressions when defining symbology key values is being considered for a future release. I would be quite interested to hear from you (and others) comments on the following: How often do you store graphic symbology…

Erik, In the Bentley Geospatial Administrator the purpose of the "Display Name" setting for both feature classes and their business properties is to provide support for XML compatible class and property names. As you know XFM feature class and property…

Erik, You were quite close. In your sample it appears that the text string element contained in the BelaegArtTekst_xfm cell had an extra space at the end after the bracket. There was also an unnecessary "Replacement Text" symbology setting. Attached…

...in your schema, just replace the system.math.round() function references with the equivalent xfm.round() function as necessary. Regards, Jeff Bielefeld [Bentley]

In an effort to broaden the communities knowledge of the Property Based Annotation capabilities available in Bentley Map, I've posted a new " Using Property Based Annotation (PBA) Replacement Text During Interoperability Imports " wiki article which provides…

Tom, You can use Property Based Annotation replacement text with any business property, including those that are queried from a database. See the " Using Property Based Annotation (PBA) Replacement Text During Interoperability Imports " wiki article…

...if using system.math.round function, please be aware of the following Known Issues from recent releases... "Workspaces with schemas containing references to the System.Math.Round C-Expression will encounter unexpected "Expression handler error…