Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#1944 closed defect (fixed)

when the map's layers are from different schemas, the features can't be selected

Reported by: christinebao Owned by: Christine Bao
Priority: medium Milestone:
Component: Web API Version: 2.1.0
Severity: trivial Keywords:
Cc: External ID: 1447700

Description

Report from Autodesk QA:

QA ever tried on FDO Postgis and FDO SQLserver2005. The data store used as test data contains multiple schemas. steps:

  1. In Studio, create a feature source, connecting FDO Postgis data store.(server: acrdmapdb3; usr/pwd: postgres/postgres; datastore: SAN_forAIMS_systemtesting)
  2. create a layer named water for feature class: Default:water
  3. create anotehr layer named zipcode for feature class: Sanfrancisco:sfzipcodes
  4. create a map, adding layer water and layer zipcode into it.
  5. preview the map (no matter basic viewer or flexible web viewer)
  6. try to select a feature on any layer

result: the feature can't be selected/highlighted. In selection panel, it seems that all the features on that layer are retrieved.

expectation: the target feature is selected.

regression: N workaround: N

Attachments (1)

Fix1944.patch (3.8 KB ) - added by christinebao 12 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 by christinebao, 12 years ago

This defect is caused by the Map.cpp, void MgMap::BulkLoadIdentityProperties(MgFeatureService* featureService)funtion. It assumes that one feauture source only has one schema, so throws exception in this case. To fix it, the map structure should be modified and add a schema level.

by christinebao, 12 years ago

Attachment: Fix1944.patch added

comment:3 by christinebao, 12 years ago

Resolution: fixed
Status: newclosed

Fixed in trunk in r6477.

comment:4 by christinebao, 12 years ago

Fixed in 2.4Jedi branch in r6478.

Note: See TracTickets for help on using tickets.