microsoft / microsoft/Dynamics365Commerce.Solutions

[RTS] InvokeExtensionMethodRealtimeRequest/ InvokeExtensionMethodRealtimeResponse Not working in UAT

Open
#397 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
80
Forks
38
PR merge metrics
No merged PRs in 30d

Description

RTS API Behavior Issue

Summary

Describe the issue
We have created one RTS method extension on FnO side for the customer save and using that we created another one for searching the customer using the Chinese name but somehow this RTS method not working on UAT at all and only giving me Communication Exception error only in the response on the call of the API.

Version and Error Info
Commerce SDK Component: Commerce SDK / Ecommerce
Component Version: 9.56
Exception/Error Details:
{
"@odata.context": "https://scuob1gz3p697542003-rs.su.retail.dynamics.com/Commerce/$metadata#Edm.String",
"value": "ERROR: CommunicationException | Service response does not contain any data."
}

Screenshots

UAT : response:

Image

PROD : response:

Image

On Prod it the connection working and shows that the problem is with the method but on UAT it shows the Communication Exception error.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the InvokeExtensionMethodRealtimeRequest/InvokeExtensionMethodRealtimeResponse call described in the issue and compare the UAT and PROD responses for Commerce SDK/Ecommerce 9.56. Reproduce the request in UAT and inspect the service response to identify why it returns CommunicationException; done means the extension method returns data in UAT or the environment-specific failure is documented with actionable evidence.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.