It would be great if we could use the surrounding object as a variable in xpath expressions, so we do not have to create a datasource nanoflow or microflow
Similar to how we can use surrounding objects in visibility, editability and validation expressions since 8.1:
When you introduce a nested data view, there will now be less of a “hard border” on your page. That means you can use objects of all the surrounding data view widgets in your visibility, editability, and validation expressions (and not only the enclosing data view). You can do this by referring to the data view name as a variable.