Hi
The Databrowser in BMAP SS2 acts different (and wrongly ??) compaired with PowerMap SS1.
Look at the screen dump. The same feature has different values in the property BrøndNr.!!!
What have I done:
Started the databrowser changed the BrøndNr to A34S420-2 pushed the save icon and then closed the databrowser.
Then I started the Analyze tool and saw that the value in property BrøndNr had not changed !!
Then reopen the databrowser and to my horror sees that the property according to the databrowser is changed !!!
So somewhere there must now be to different sets of property for the same feature --I have tested that the databrowser actually locate the same feature as I have used the Analyzer on.
Please help quick or we have to stop the migration from PowerMap SS1 to Bentey Map SS2
Erik Wirring
Hmm!
it looks like the same error is in PowerMap SS1
Just tried this in Bentley Map SelectSERIES 1 (08.11.07.113) and Bentley Map Enterprise (SelectSERIES 2) and could not reproduce. It behaved as expected.
Can I( get a copy of the drawing you are using ? Also is the attributes stored in the drawing or in a database ? If a database, then I would need a dump of that also.
Ok guys,
I finally be able to reproduce it in SS1 and SS2. I logged TR 313199 which said:
"[XFM] Editing attribute of an accented character property name don’t give expected display result in analyze window."
Thanks Erik for reporting it.
Sebastien
GeoSpatial QA
It has been fixed and verified in Bentley map 8.11.7.428.
Please notice the wrong properties names added cannot be remove. See the following notice from Development Team:
"When a property with accented character was edited in the DataBrowser, the name was not correctly decoded and a new property with the wrong name was added to the feature instance. This issue should be resolved with this fix, but existing instances which already contain a wrong property name still have it.
We do not have a function to remove a property from an instance in our API. The users could use the “Add>Schema Versioning” option for a feature in GSA and create an XSLT that will remove the bad property. The xslt would be run during feature reset command, or they could use the platform MDL API to modify the Xml fragment directly. See mdlXml platform API. They could also use xfmElement_isFeatureXmlFragment to identify the elements to update."
HTH,