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

[jng]

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.

[jng]

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.

[ksgeograf]

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

[jng]

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.

[ksgeograf]

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