We have two SharePoint lists on a site, call them List1 and List2. List2 contains a text field containing names of people (Name, but also the Title) and a Boolean field indicating whether they have died (Deceased). List1 has among other fields a Person field with a lookup to Azure AD (Person) and a field that looks up the names of people in List2 (Visited), allowing several to be selected. I wanted to filter out the deceased from the selections available in Visited. I quickly abandoned customising the .aspx files using SharePoint Designer 2013 as instructions on the internet appeared obsolete. It seemed that PowerApps was the right approach, but I have hit several issues. I have had many attempts at getting this to work, and may now have ended up with a corrupt PowerApps environment.
Isssues:
- The out of the box custom form for List1 only puts the Person and Visited fields on the form. When I first tried this, all the custom fields were put on the form.
- Attempting to save a new value fails with a possible data source error.
- The out of the box fields don't recognise the other data sources:
Person Item Formula is of the form Choices([@List1].Person) - no reference to the AD lookup, so presumably you can only enter people who are already in List1.
Visited Item formula is of the form Choices([@List1].Visited) - no reference to List2, so presumably you can only enter Visited who are already in List1. - Changing this to Choices(List2.Name) results in a Name isn't valid error, despite Name being in the selection lists for List2 fields.
Hence, I am stuck, and am tempted not to put more effort the project as the issue is not so great. It does, however, make me hesitate to recommend SharePoint custom lists (as opposed to other ways of storing data that might me more familiar to end users) and attempting to use PowerApps to manage them.
Any comments?