07-07-25 01:01 PM
Hi Everyone,
I'm encountering an issue when using the Microsoft Graph – SharePoint VBO from the Digital Exchange (DX) to retrieve items from a SharePoint list.
When executing the Get items in a list action, the query string appears to be stripped from the URI. Specifically, this endpoint is expected:
/sites/[Site ID]/lists/[List ID]/items?expand=fields
However, based on Fiddler logs, the request sent from Blue Prism does not include the query string (?expand=fields).
From what I can see:
- The code stage looks correct.
- This leads me to suspect that the issue may lie in how the URI is being compiled or possibly in how the DLL parses the request.
Is this a known issue, or is there a workaround for preserving query strings in this scenario?
- Edition: Windows 11 Enterprise
- Version: 24H2
- Installed on: 19/03/2025
- OS Build: 26100.3194
- Experience Pack: 1000.26100.48.0
- Version: 7.4.0
- Name: Microsoft Graph – SharePoint
- Build Date: 2024/07/18
- Version: v3.1.0
- Used in Blue Prism Version: 7.3.0
- Action: Get items in a list
- Endpoint: /sites/[Site ID]/lists/[List ID]/items?expand=fields
Note: The above query string is missing in the actual request sent.
- Action: Send Request
DLL Referenced:
C:\Program Files\Blue Prism Limited\Blue Prism Automate\roslyn\System.Net.Http.dll
Captured via Fiddler:
Fiddler confirms the query string is not present in the outgoing request from Blue Prism. But I am able to get the expected response when making the request from Fiddler.
Fiddler capturing the request sent by Blue Prism
Request made in fiddler including response
Any insight or suggestions would be greatly appreciated!
Thanks in advance for your help.
07-07-25 05:33 PM
Having given some time to this issue today, I have been able to identify the problem. Due to the name of the Microsoft SharePoint VBO and an old install of the Microsoft SharePoint API being exactly the same the selection when selecting the action from the dropdown was forcing the selection onto the API.
08-07-25 06:35 AM
Hello Robert - i raised the same issue few month back on same name for Web API and VBO. it cause conflict.
https://community.blueprism.com/t5/Product-Forum/VBOs-with-same-name/td-p/117564
21-07-25 02:54 PM
Hi @robert.rudd
Yes, there are two objects with the same name but different object IDs. The older Web API variation of the SharePoint connector should be removed/archived from your system. It is no longer supported.
Cheers,
Eric