Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#804 closed defect (invalid)

Layer editor does not set selected schema (feature class) if the feature source has multiple feature classes

Reported by: jng Owned by: ksgeograf
Priority: low Milestone:
Component: Maestro Version:
Severity: major Keywords:
Cc: External ID:

Description

If you have a feature source that contains more than one feature class.

When opening a layer definition that references that feature source, the "Schema" field on the layer editor stays at the first feature class. It does not get set to the actual referenced feature class.

Change History (5)

comment:1 by jng, 16 years ago

Summary: Layer editor does not set selected schema (feature class) if the feature source has multipleLayer editor does not set selected schema (feature class) if the feature source has multiple feature classes

comment:2 by jng, 16 years ago

Resolution: invalid
Status: newclosed

I'm seeing the same thing in MG Studio, so it could be something to do with the way I'm generating these layers. Closing for now.

comment:3 by ksgeograf, 16 years ago

Does the featuresource have special charaters, like _,;: or spaces?

comment:4 by jng, 16 years ago

I was programatically creating my layer definitions, but I was not using the fully qualified feature class name. Which MapGuide probably then thought to change it to the first known feature class in that feature source.

comment:5 by ksgeograf, 16 years ago

Version: 2.0.1

Yes, the shorter forms usually work (provider dependant). But the GUI tries to locate the full string instead.

Note: See TracTickets for help on using tickets.