Create a multi node tree picker targeting members.
Add that property to a document type.
Create members to test with.
Select members on node and publish.
Queue this change for transfer and transfer it.
Check the environment it was transferred to.
On review it seems this will work as expected when the appropriate configuration for deploying members is in place, but if you are testing by deleting the member in the upstream environment and re-deploying from downstream, it'll fail as Deploy considers the member to already exist.
This manifests itself in the following issue:
CMS: Cms 13.4.0 Forms 13.1.2 Deploy 13.1.0
On review it seems this will work as expected when the appropriate configuration for deploying members is in place, but if you are testing by deleting the member in the upstream environment and re-deploying from downstream, it'll fail as Deploy considers the member to already exist.
This item has been added to our backlog AB#42610