Microsoft Search vertical
Found it! 😁 Actual screenshots of the Microsoft Search Vertical configuration wizard in SharePoint Online.
1. Query configuration
Or where we configured 110.
Found it! 😁 Actual screenshots of the Microsoft Search Vertical configuration wizard in SharePoint Online.
1. Query configuration
Or where we configured 110.
Playbooks: Eight-Hour SPO Search Investigation
A proper feline release scale
This should be my go to Guide for when I think that there is usually a better way. But not when you work with Microsoft Dev Tools
https://www.reddit.com/r/sharepoint/comments/1gowu0w/sharepoint_rest_api_authentication/
Maybe I can make a list of Solutions as I find them. This one seems clear enough:
The Cat's Ass indeed! 😸
And you've arrived at a remarkably sensible architecture:
We have an existing SPO metrics list, populated automatically by user activity, and we want to produce a straightforward report from that data.
No new data collection, no migration, no unnecessary infrastructure. And no unnecessary charges!
|
Option |
|---|
For the extractor, the realistic Microsoft/O365 options are:
|
Option |
What it is |
Good fit here? |
|---|---|---|
|
Microsoft Graph API |
Direct API access to SharePoint content |
Very strong |
|
SharePoint REST API |
Goal: Prototype metadata tagging as a practical way to manage 500–1,000 pages in SharePoint Online.
Demo scope: One task only: tag documents and demonstrate grouping by those tags.
A missing Contact link is preferable to a confidently wrong Contact link.
Contact lookup prototype
Below is the working path, the exact JSON snippets, and the known troubleshooting points. This is intended as a practical Monday reference, not a redesign.
Start here:
/sites/ORG-6579-0004/Lists/702pbtoc1/AllItems.aspx?viewid=40eaccfa-51d2-46ab-922f-6c9bcb6cae5c
This is:
This prototype is to demonstrate that SharePoint Online can support this requirement without requiring users to manually copy a Contact value and perform a separate search.
The current cross-reference table is intentionally used as a non-invasive proof of concept. It allows us to demonstrate the routing logic without changing the existing Playbook or Contacts structures.
The three terms provide:
The three terms turn an inherited folder structure into searchable meaning
SharePoint Managed Metadata provides a controlled vocabulary that describes what a document is about, independently of the words that happen to appear in the document.
For the prototype, three Term Store concepts provide the semantic structure:
Centre · Region · Activity
Status CHECK
F12
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.”
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
Python HTTP-triggered Function.
We need a design layer that captures the screen before Power Apps turns it into controls and properties.
For this POC, let's keep three note layers:
allison@frodo:~/projects/azure/Camelot$ cd ~/projects/azure/Camelot
python3 -m venv .venv
source .venv/bin/activate
python --version
Python 3.12.10
((.venv) ) allison@frodo:~/projects/azure/Camelot$
Our first working mission:
Arthur submits a valid Quest containing an artist and one or more album names. Lancelot conducts the research in Azure and returns proposed covers, sources, and any side loot discovered.
For example: