No Http Resource was found that matches the requst URI ""http://abc.operations.dynamcis.com/data/custcustomers " No route data was found for this request

(1) Share

Report

Posted on by Community Member

Hello Everyone ,

i am working with d365 FO integration usinmg odata with D365 Fo entities.

incase my senarion i am simple entity . when i try to load http://abc.operations.dynamcis.com/data/custcustomers i am getting below error

No Http Resource was found that matches the requst URI ""abc.operations.dynamcis.com/.../custcustomers " No route data was found for this request

I tried checking is my entity listed under http://abc.operations.dynamcis.com/data/ but on first attempt y entity was not listed . after doing multiple attempts of brwosing then my entity got listed.

like wise my facing issues with inconsistency in loading my odata entity first attempt which i caused application intgeration break up. on continues re attempt it got loading not sure what might stopping it load on first attempt.

any one experienced similar issue and any thoughts would be really helpful

All responses (7)

Answers (1)

Community Member on at

Like (0)

Report

RE: No Http Resource was found that matches the requst URI ""http://abc.operations.dynamcis.com/data/custcustomers " No route data was found for this request

Hello all,

Finally I could able fix it by redeploying my pakcage onto production environment and build it.

Regards,

Praveen
Verified answer

Fangyuan Hou on at

Like (1)

Report

RE: No Http Resource was found that matches the requst URI ""http://abc.operations.dynamcis.com/data/custcustomers " No route data was found for this request

Hi Praveen,

Please feel free raise a support ticket to us, we can have a further check on this, we haven't see such issue before.
Gunjan Bhattachayya 35,421 on at

Like (0)

Report

RE: No Http Resource was found that matches the requst URI ""http://abc.operations.dynamcis.com/data/custcustomers " No route data was found for this request

Hi Praveen,

Since it works as expected on Sandbox and you are seeing the issue on Production only, you should open a case with MS support to look into this.
Community Member on at

Like (0)

Report

RE: No Http Resource was found that matches the requst URI ""http://abc.operations.dynamcis.com/data/custcustomers " No route data was found for this request

Hello Gunjan,

It's not timing out. It's only giving http resource not found that uri your trying load error on first time we browse and continuously we browse the same on second time we are able to load it again.

This was working on sandbox as expected . But on production where we see this issue.

Regards,

Praveen
Gunjan Bhattachayya 35,421 on at

Like (0)

Report

RE: No Http Resource was found that matches the requst URI ""http://abc.operations.dynamcis.com/data/custcustomers " No route data was found for this request

HI Praveen ,

Is it timing out in your Dev environment and working in Sandbox? In that case, you might want to check the resources allocated and if increasing the same resolves your issue.
Community Member on at

Like (0)

Report

RE: No Http Resource was found that matches the requst URI ""http://abc.operations.dynamcis.com/data/custcustomers " No route data was found for this request

Hello Gunjan,

Thank for your reply.

Yes mine custom entities not only customer we have entities created extensions for other ones like item, sales transaction etc.

Same working on sandbox environment fine.

Yes, my entities public collection name is custcustomers. As I mentioned it was loading few times and few times not.

I am using PU 39 version of FO.

Regards,

Praveen
Suggested answer

Gunjan Bhattachayya 35,421 on at

Like (0)

Report

RE: No Http Resource was found that matches the requst URI ""http://abc.operations.dynamcis.com/data/custcustomers " No route data was found for this request

Hi Praveen,

Do you have an entity with public collection name CustCustomers? Assuming you are on the latest version, you would need to use the entity "CustCustomerV3Entity" which has a public collection name "CustomersV3". You will need to use this URI - abc.operations.dynamics.com/.../CustomersV3 and check if you are still getting the error.