If I need to add or update features in the database, I need to re-register the features in my Oracle connection in GSA. Every now and then this changes the case of my db-properties to uppercase. After that my criterias stops working since they are case sensitive. I've also seen other strange things happen after a re-register that caused my project to stop working.
Any comments or ideas?
Regards,
Krister
When you register the features and get to the part of the wizard that allows you to change the display name of the feature/attribute, do you change the names here, or do you rename them after they are registered and listed in the XFM project tree ? Most generally, I advise to change the display name and not the actual attribute name.
Just wondering .....
Also , what version of Bentley Map are you using, I see the following TR filed just a few weeks back.
TR# 336558
During the register features process we have found that the Feature and Attribute names are being changed from uppercase to mixed case.
This causes several problems when trying to configure a schema. For example CRITERIAs that search for attributes using an all uppercase name will fail.
Note: Only the Name (name) and not the Display Name (alias) or Label (label) need to remain uppercase.
This was filed against version 08.11.07.460 of Bentley Map in March.
I'm running SS2 so I'll just hope this TR will be handled ASAP :)
/Krister
Owner consultant at Surell Consulting AB
But, after reading your post a couple more times and the write-up in the TR, it sounds like you are wanting it to remain mixed case and the TR submitter wants it to revert back to all upper case. Maybe I am wrong,
Krister,
During the register feature process you may not be aware that you can select one or more feature class names or business property names and then right-click and choose to change the case as shown in the following:
Does this capability help your particular situation?
Another issue you mentioned was the fact that you seen strange things happen after you re-register that caused your project to stop working. In the upcoming Bentley Map V8i (SELECTseries 3) 08.11.09 release, we resolved TR 334831 which is described as "[Administrator] The "Register Feature" process fails to preserve metadata for previously registered feature classes when geometry types cannot be determined, resulting in failed post operations". During resolution of that issue we determined that if you started the register feature process, then cancelled the wizard but later changed something else in your schema and then saved the schema, the information for the registered features could become incorrect, thus causing unexpected behaviors. As noted, this issue has since been resolved.
Jeff Bielefeld [Bentley]