albertwgchu
albertwgchu
This functionality is supported. We use parent child relationships and it works fine.
In case this helps anyone, we had a single store with multiple layers which were reading from different geometry fields. Adding a separate store for each geometry avoided this issue.
We've encountered the same issue as you describe. We use javascript to strip out the layer id prefix as a work around. I'm not sure if the layer id prefix...
> I'm quite surprised this crippling bug is still here four years later. Attempting workaround by putting a version number in the payload application side and using an ES pipeline...
I think I have encountered this as well when using a data set that doesn't have incrementing field name in the entire data set. In my case it was legacy...