"Resource not found" error in PowerApps custom connector

(1) Share

Report

Posted on by Inkey Solutions

112

Hello everyone,

I have an API url which executes and returns results sucessfully in Postman. But I am getting belo error when I am trying to execute it from PowerApp custom connector.

For creating custom connector in PowerApp, I am taking help of below links:-

https://docs.microsoft.com/en-us/connectors/custom-connectors/create-postman-collection

https://docs.microsoft.com/en-us/connectors/custom-connectors/define-postman-collection

Please help.

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (1)

v-micsh-msft on at

Like (2)

Report

Re: "Resource not found" error in PowerApps custom connector

I think the issue here should be related to the resource URL configrued within the Connector.

You may need take a fiddler trace to see if the connector has send the correct record to the correct Server address.

Please verify the Request part under the Definitions phase when building the Custom connector, see if the request parameter and the Request URL has been configured correctly.

Regards,

Michael

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Re: "Resource not found" error in PowerApps custom connector

This is extremely frustrating. I've tried setting up all kinds of simple HTTP calls, and always get this 404 error.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Re: "Resource not found" error in PowerApps custom connector

Hi @v-micsh-msft. Will you provide a link to how to perform a Fiddler trace? This info is tough to find.
Thank you

Was this reply helpful? Yes No
Verified answer

v-micsh-msft on at

Like (1)

Report
Re: "Resource not found" error in PowerApps custom connector

Hi @ericonline,

Have you tried the following?

"

How to Capture Fiddler Trace

Environment

Service Third-party product

Description

This article provides the general steps for capturing HTTP/HTTPS traffic with Fiddler and saving it as a log file on your local machine.

IMPORTANT: When started, Fiddler captures all HTTP and HTTPS traffic, including some sensitive information. Do not share Fiddler logs outside of the private support communication channels (e.g., support tickets).

Solution

Download Fiddler from here and install it.

Run Fiddler and go to Tools -> Fiddler Options.

On the HTTPS page, verify that Capture HTTPS Connects is enabled.

Verify that Decrypt HTTPS traffic is enabled with the ...from all processes option.

Minimize Fiddler to tray.

Replicate the reported issue.

In Fiddler, go to File -> Save -> All Sessions and save the archive to disk.

This will produce a SAZ file, which you will be able to archive and share with the support personnel.

Notes

If the produced Fiddler log doesn't contain HTTPS traffic records, make sure that the Fiddler Root certificate is trusted on your machine.

"

quoted from here.

Another blog talking about how to generate the Fiddler trace:

Capture http(s) traffice with http Fiddler

Regards,

Michael

Was this reply helpful? Yes No
joaorsfonseca 11 on at

Like (0)

Report

not found 404 on another azure directory

I'm facing the same error but with a little difference..

I have an API with AzureAD enabled, and i want to allow in an different AAD to have access to it.

In API's app registration I've exposed and enabled the access to the other user app registration. In postman it works, but while testing in his custom connector i'm getting the 404 not found.

I've also tried to check the https requests under Fiddler, but no luck there.

Any tip?

Was this reply helpful? Yes No