web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Copilot Studio - Calling Actions from Copilot S...
Unanswered

Sap Odata Connector strange behaviour

(1) ShareShare
ReportReport
Posted on by 505
Hi, i have just now created a copilot studio Agent that should call the SAP OData connector.
 
I am connecting via APIM Service to SAP which works fine as described in Martins blog. Hurray🎉 SAP OData connector now supports OAuth2 and SAP Principal Propagation
 
I am facing a very strange issue however. The agent is building my query strings - also fine (Base URI of the connector is my APIM)
 
This it the log i see in APIM 
 
each query gets the ?$top=5 or anything else after the ? "deleted" and there is this silly forwardslash added to each query
 
For me this indicates that the SAP OData Connector is not passing the Query over the Internet? (i am not sure tho)
 
Does anyone have any help for me ?
I have the same question (0)
  • Suggested answer
    DAnny3211 Profile Picture
    63 on at
    Sap Odata Connector strange behaviour
    Hi,
    
    It sounds like you're encountering an issue where the **OData query parameters** (such as `?$top=5`) are being stripped from the request when routed through the SAP OData connector via APIM. Additionally, the unexpected addition of a trailing slash (`/`) in the query path may be interfering with how SAP interprets the request.
    
    Here are a few things to check:
    
    1. **Connector configuration**: Ensure that the `OdataQuery` parameter is explicitly defined and passed separately from the `relativePath`. Some connectors require query parameters to be set in a dedicated field rather than appended directly to the path.
    
    2. **APIM rewrite policies**: Inspect the inbound and outbound policies in your APIM instance. It's possible that a rewrite or transformation policy is unintentionally modifying the URL structure or stripping query parameters.
    
    3. **SAP OData endpoint behavior**: Some SAP services are sensitive to URL formatting. A misplaced slash or missing query string can lead to unexpected behavior or default responses.
    
    4. **Reference documentation**:
       - SAP OData connector setup
       - Azure API Management policies
       - Martin's blog post #127881 — if available, this may contain specific guidance on OAuth2 and Principal Propagation.
    
    You might also consider logging the full request before it hits APIM to confirm whether the query string is present and correctly formatted.
    
    Thanks and best regards,  
    Daniele  
    **Note: This response was prepared with support from Copilot to ensure clarity and completeness.**

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Tom Macfarlan – Community Spotlight

We are honored to recognize Tom Macfarlan as our Community Spotlight for October…

Leaderboard > Copilot Studio

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 398 Super User 2025 Season 2

#2
Romain The Low-Code Bearded Bear Profile Picture

Romain The Low-Code... 262 Super User 2025 Season 2

#3
chiaraalina Profile Picture

chiaraalina 100

Last 30 days Overall leaderboard

Featured topics