Guest user/role - strange issue #2, solved

As mentioned yesterday we encountered a strange issue related to guest users/roles. Basically it seemed that it is not possible to create a new feature (no matter for which feature class) when working with an guest user/role in our job enabled LandManagement industry model. Instead my colleague got an error message regarding a missing spatial index. Confusing was, that it seemed to work when using a Map-Admin user. Further confusion was caused by the fact that when working directly on the data user the problem did not occur either. When I performed a test on my computer I was not able to reproduce the issue at all.  

As it turns out our testing was not so comprehensive as it should have been in the first place and with hindsight the behaviour we observed can be explained.

Culprit seems to be a setting in Map's Global Enterprise Industry Model options (setting is replicated in IM options) : "Vicinity For Digitising Points [m] "

If "Vicinity For Digitising Points [m] " is turned on we get the error message, otherwise we don't. The setting itself is probably not to blame - we actually misunderstood the meaning of the option and can now safely turn it off. I think the option will cause Map to look through all point feature classes and if one of them doesn't have a spatial index one will get the error message.....

The issue is not related to topologies or guest user or non Map-Admin user. As we used different Map users and different industry models (data or guest user) during testing the aformentioned option was not uniformly set, caused therefore different results.


Map 2013, SP2

Guest user/role - strange issues

We had two strange issues in AutoCAD Map related to guest users/roles (SecurityAdmin). Complexity is raised by the fact that we also have an job-enabled industry model and a topology.

Issue #1
Map crashed when we deleted a feature in "Live" state (from a certain feature class beloging to an area-topology)  when using a guest user/role (SecurityAdmin). 

The feature actually got deleted - the issue was the crash.

CER report and Map log file contained the following piece of information:

System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
 bei Autodesk.Map.IM.Data.FeatureClass.GetChildrenFeatureIDs(IEnumerable`1 fids, HashMap`2 parentToChildren, Int32 depth, Boolean geometryFeaturesOnly)
 bei Autodesk.Map.IM.Map.MapLogicImpl.RegenenerateFromModificationLog(Boolean regenerate)
 bei Autodesk.Map.IM.Map.MapLogicImpl.MapDrawBurstDisposed(MapDrawBurstImpl burst, Boolean disposing)
 bei Autodesk.Map.IM.Map.MapDrawBurst.Dispose()
 bei Autodesk.Map.IM.Map.MapLogicImpl.DeleteFidTidArray(FidTidArray fta)
 bei Autodesk.Map.IM.Map.MapLogicImpl.DeleteFeatures(String prompt)
 bei Autodesk.Map.IM.Map.MapDocument.Delete_Interaction(Object sender, InteractionEventArgs e)
 bei Autodesk.Map.IM.CommandRegistry.API.BaseCommandRegistry.Execute(String globalName, CommandExecute commandCallback, Boolean async, Document document, Object[] args)
 bei Autodesk.Map.IM.CommandRegistry.API.BaseCommandRegistry.Execute(String globalName, Boolean async, Object[] args)


 This issue has been resolved by re-creating the Guest-user/role in SecurityAdmin.

Issue #2

It was not possible to create a new feature (for a certain feature class beloging to an area-topology) in an "open" job when:

- using a guest user/role (Security Admin)
and
- using a non-Admin Map user.

We got the following error message : 

Vorgang ist fehlgeschlagen, da ein Spatial-Index nicht in der Fachschale vorhanden ist.

(Industry model does not have a spatial index. )

No message appeared in Map's log file.

There was no issue creating the feature when logging in with a Map user who has Admin permission (Map-Admin, not Windows or Oracle Admin). 

My colleague showed me the issue on his machine yesterday. He had done several tests over the last two days. The issue always occured whilst testing. Today I did a test on my machine and the issue did not occur. Then my colleague did test on his machine again and got the same result.. We tried to find out if the issue is related to a certain workflow but to no avail. 

Map 2013, SP2

Feature with wrong geometry type for feature class

We had one feature (Industry Model) which was not displayed in Map. 1 Click Maintenance reported an unsupported geometry type for a polygon feature class. A closer look unveiled that the feature had been migrated as line feature and not as polygon feature:
  

Line string feature in a polygon feature class (Map Industry Model)

The geometry itself was correct - so it could not be "repaired" in Oracle Spatial. Here is one way to solve the issue:


1. connect via FDO Oracle and add feature class to Map 
   FDO Oracle will create a layer containing lines and polygons - the feature in question will therefore be displayed in Map.

Adding table via FDO Oracle - line and polygon features are displayed

2. save layer as sdf, add sdf to Map and remove layer based on FDO Oracle from Display Manager
3. rectify geometry in SDF based layer - for instance via "extract geometry" 
4. open form for Industry model feature where geometry type is incorrect
5. link rectified geometry with feature - confirm "Feature has already a geometry - replace?" 

Map 2013, SP2