Skip to main content

Notifications

Community site session details

Community site session details

Session Id : ASHXrRf97xHsaC3PYwKIp5
Power Apps - Microsoft Dataverse
Unanswered

([Bad Request], The remote server returned an error: (400) Bad Request.), AX export encountered an error

Like (0) ShareShare
ReportReport
Posted on 5 Nov 2019 06:42:58 by 156

Scenario: We currently have a system on Dynamic 365 Finance for Operation, and we want to connect PowerApps to transfer data from 365 to CDS. We followed this tutorial: https://docs.microsoft.com/en-us/power-platform/admin/data-integrator

 

So far these are the steps that we did:

1. We created an entity in PowerApps with some fields that match the entity in 365

2019-11-05_11-58-06.png

2. We created two connections for the PowerApps CDS and the Dynamic 365 For Fin & Op

2019-11-05_10-29-37.png

3. In Admin Center -> Data Integration -> Connection sets, we created a new connection set that include the two connections above. 

2019-11-05_10-34-13.png2019-11-05_11-54-10.png

4. Later on we created an integration project that use the above connection set 

2019-11-05_11-49-39.png

5. We created a task 

2019-11-05_11-55-59.png

6. Finally when we ran the project, we got the following error 

2019-11-05_11-51-30.png

we did a quick search and found a similar article: https://powerusers.microsoft.com/t5/Common-Data-Service-for-Apps/The-remote-server-returned-an-error-400-Bad-Request-AX-export/td-p/322605

 

We tried to wait but it did not change anything, we still got the same problem. 

Categories:
  • Community Power Platform Member Profile Picture
    on 14 Apr 2020 at 17:51:07
    Re: ([Bad Request], The remote server returned an error: (400) Bad Request.), AX export encountered an error
    Have you found resolution to this issue? Im having same problem at the moment.

    I have admin rights, project is running timed and tried it manually (both gives same error). I have only one entity and not all fields from it.
  • nickmanny Profile Picture
    18 on 27 Jan 2020 at 06:14:28
    Re: ([Bad Request], The remote server returned an error: (400) Bad Request.), AX export encountered an error

    The 400 Bad Request error is an HTTP status code indicates that the request you sent to the webserver was malformed , in other words, the data stream sent by the client to the server didn't follow the rules. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed. There are a number of different causes for a 400 Bad Request Error . It might be a malformed request syntax, invalid request message framing, or deceptive request routing . In most cases, the problem is on the website itself, and there's not much you can do about that. To fix a 400 Bad Request error it is best to start diagnosing the issue from the client side itself. Complete the steps outlined in this section to help diagnose and correct the error.

     

    Check for errors in the URL.
    Clear Browser Cache and cookies.
    Clear DNS Cache.
    Check your File upload Size.
    Deactivate Browser Extensions.
    Contact the site owner to report the 404 error.

     

  • MinhPham96 Profile Picture
    156 on 07 Nov 2019 at 10:05:36
    Re: ([Bad Request], The remote server returned an error: (400) Bad Request.), AX export encountered an error

    Dear @v-yutliu-msft , thank you for your response, we want to update some information based on your questions. 

     

    1)whether your firewall block this service

    Both the Dynamic 365 and PowerApps are stored on clouds and under the same organization. There should be no problem linking the two, if there is a possible firewall, can you give us some information ? 

     

    2)whether you have access to these two data source

    We used the admin account for this project and it has full access to the data source.

     

    3)whether your file is too large

    We just perform some data transfer between the entities, so no large file transfer or anything. 

     

    Thank you and Regards

  • v-yutliu-msft Profile Picture
    on 06 Nov 2019 at 03:03:49
    Re: ([Bad Request], The remote server returned an error: (400) Bad Request.), AX export encountered an error

    Hi @MinhPham96 ,

    400 bad request generally comes when you can't access the resource.

    Please check:
    1)whether your firewall block this service

    2)whether you have access to these two data source

    3)whether your file is too large

    Here's a blog about 400 bad request for your reference:

    https://airbrake.io/blog/http-errors/400-bad-request

     

    What's more, you could also try to clear your browser's cache.

    If the problem still exists , I suggest you ask for help here:

    https://powerapps.microsoft.com/en-us/support/pro/ticket/

     

     

    Best regards,

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

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Congratulations to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard > Power Apps - Microsoft Dataverse

#1
stampcoin Profile Picture

stampcoin 15

#2
ankit_singhal Profile Picture

ankit_singhal 11 Super User 2025 Season 1

#3
mmbr1606 Profile Picture

mmbr1606 9 Super User 2025 Season 1

Overall leaderboard

Featured topics

Loading started