Using Microsoft Graph Explorer to Debug SharePoint Filters in Link Enterprise
4 min

1. Purpose
Demonstrated how to use Microsoft Graph Explorer to debug SharePoint filters in docuflow middleware. This helps identify whether issues originate from Microsoft Graph or the middleware layer.
2. Tools & References
- Graph Explorer: https://developer.microsoft.com/en-us/graph/graph-explorer
- Demo Tenant: (yourtenant).sharepoint.com
- Sample Site ID: https://graph.microsoft.com/v1.0/sites/(yourtenant).sharepoint.com:/sites/VFSGMiddleware
- Sample Library: /VFSGMiddleware/Equip/
3. Benefits of Using Graph Explorer
- Test filters instantly without restarting middleware
- Isolate root causes between Graph and docuflow
- Discover internal SharePoint field names
- Simulate customer scenarios for debugging
4. Corrected Graph API Filter Example Correct Syntax:
https://graph.microsoft.com/v1.0/sites/.../list/items?$expand=fields&$filter=fields/SAPFacility eq 'Complete' and fields/docuflowSaplinkError0 ne 'True'
URL-Encoded Version (for code):
...?$expand=fields&$filter=fields/SAPFacility%20eq%20'Complete'%20and%20fields/docuflowSaplinkError0%20ne%20'True'
5. Boolean Field Values
Value | Boolean |
|---|---|
0 | False |
1 | True |
6. Common Pitfalls
Mistake | Result |
|---|---|
Using = instead of eq | Filter ignored |
Missing fields/ prefix | Query fails or returns incorrect results |
Unindexed fields | Filter errors unless workaround header used |
Null Boolean values | Ignored by Graph API |