cancel
Showing results for 
Search instead for 
Did you mean: 

Microsoft Graph – SharePoint VBO: Query String Missing from URI in List Retrieval

robert.rudd
Level 2

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.

🔍 Issue Summary

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.

Has anyone experienced this before?

Is this a known issue, or is there a workaround for preserving query strings in this scenario?

💻 Technical Details

OS

- Edition: Windows 11 Enterprise
- Version: 24H2
- Installed on: 19/03/2025
- OS Build: 26100.3194
- Experience Pack: 1000.26100.48.0

Blue Prism

- Version: 7.4.0

VBO Information

- Name: Microsoft Graph – SharePoint
- Build Date: 2024/07/18
- Version: v3.1.0
- Used in Blue Prism Version: 7.3.0

Action Details

- 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

🔧 Additional Details

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

robertrudd_1-1751889616192.png

Request made in fiddler including response

robertrudd_0-1751889616187.png

 


Any insight or suggestions would be greatly appreciated!
Thanks in advance for your help.

3 REPLIES 3

robert.rudd
Level 2

Resolved

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.

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

 

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