Chapters: 
O365 Plumbing

Six months from now I probably will not remember “Dynamic filtering,” but I will remember:

“That thing where I connected two SharePoint lists without Power Apps.”

SharePoint: connect two lists on a page without Power Apps

Also searched as:
join SharePoint lists, relate two lists, master-detail, filter one list from another, connect list web parts, relationship between lists, avoid Power Apps, taxonomy alternative

Answer:
Use Dynamic filtering on the SharePoint List web part.

Where:
Edit SharePoint page → select List web part → right-side properties → Dynamic filtering → On

Example: 

Regions.Centre
    filtered by
Centres.Title

Selecting a Centre in the Centres web part filters Regions.

Important:
This is not:

  • a Lookup column
  • a Term Store relationship
  • Power Apps
  • Power Automate

Why I care:
I previously spent nearly a week trying to reproduce this in Power Apps because searches/documentation made it appear that SharePoint could not do it.

Related terms:
SharePoint List web part, Dynamic filtering, master/detail, connected web parts, Centres, Regions

That last section is particularly important. You want to deliberately include wrong terminology you might use next time.

If you search your notes three years from now for:

sharepoint join lists

you should find this.

If you search:

term store centres

you should find this.

If you search:

that stupid thing I did in Power Apps

frankly, that should find it too. 😂

I would make the documentation problem-first

Not: 

SharePoint
  Web Parts
    List Web Part
      Dynamic Filtering

That's Microsoft's filing cabinet. You already know how well that worked.

Instead: 

How do I...
  connect two SharePoint lists
  filter Regions when Centre is selected
  avoid Power Apps for master/detail
  use a SharePoint list as taxonomy

Each of those can point to the same nugget.

And Markdown would be superb for this. Plain files, grep-able, portable, versionable, no dependency on whatever Microsoft renames next Tuesday.

You could even have a little top-level o365-plumbing.md or folder: 

o365-plumbing/
├── README.md
├── sharepoint/
│   ├── connect-two-lists-dynamic-filtering.md
│   ├── lookup-columns.md
│   └── term-store-when-to-avoid.md
├── power-automate/
└── terminology.md

I think we should document discoveries at the moment we finally identify them, especially these hard-won ones. The useful artifact isn't merely “Dynamic filtering exists.” It's the trail of words you used while trying to remember it. That's the part conventional documentation throws away.

sharepoint