I have experienced an interesting behaviour on the WMS provider when feature classes have child feature classes.
In this case the child feature classes inherit the attributes and coordinate systems (CS) of the parent feature class.
On one server we have the curiosity that one parent feature class has several child feature classes, but not the same CS than the child feature classes. The parent feature class also does not have the CS which will be returned as the one from the WMS service capabilities. But the child feature classes have this coordinate system.
For Map 3D this makes it not possible to show the feature classes (parent/child) in the data connect UI as the CS of the feature classes does not match the CS from the WMS service!
Is the above configuration valid for FDO, when the parent feature class has other CS than the child feature classes?
Why does the child feature classes inherit all the information (incl. CS) from the parent and cannot be requested alone?