I just want to confirm, a hosted feature service view can only have layers and tables from a single parent service, is that correct?
If so, is there a reason for this limitation? The layer definitions passed to the REST API addToDefiniton method contain an attribute that identifies the parent service. So, the structure of the API seems to support it.
I'm not trying to combine layers from different parent services into a single layer in my view. Instead, I'm trying to group different layers from different parent feature services into a single feature service view. For example, county layers from a US_Counties feature service and city layers from a US_Cities feature service.
I know I can accomplish this same thing, somewhat, with a webmap, but why can't I do this with a feature service view?
