When writing mappings for a MongoDB database integrated with App-Schema nested JSON paths should be evaluated relative to the parent ... and this is not happening. JSON paths are being evaluated against the root JSON attribute.
This means that everything works fine until we ave the same nested feature in a another path. The feature needs to be mapped twice since the full JSON path relative to the root JSON attribute needs to be provided.
To reproduce this issue just create a mapping with a nested feature with more than a level, the full JSON path will need to be provided otherwise no content will be produced.