From your reference screenshot, I see you have added reference set between Member and project entity and also third joining entity.
You should consider either of this way and not both.
For accessing details on the page, check in which context entity values can be fetched. In case all entities are needed and not available via direct context you can use Microflows to load data in page widgets.
As you want to fetch project details for a logged in member, make sure your Member entity is associated with Account entity.
For associating Member and Project, as its a m-n(many-many) reference, you could do a setup like below image.(Decide the ownership entity as per you requirement.)
I would prefer going through below learning path to make informed decision on impact of ownership and m-n relationship in entity model. m-n associations has performance impact if both tables are growing.
You can consider adding indexes on tables to improve performance.
I would prefer below combinations on my dataset before going for final design.
Consider below for during overall design.
You could also consider having a joining entity in case both tables are growing in data.
Thank you Vaishall.
I will also check the learning path you provided.
I have modified the domain model as shown in the attached image.
When I add a member, I want to select the project in the drop down, but the project does not appear as shown in the image below.
How can I get the project to show up on the parameters screen for the member?
Thank you in advance for your help.