Check out the latest Business Central updates!Learn about the key capabilities and features of Dynamics 365 Business Central and experience some of the new features.
Download overview guide | Watch Business Central video
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
When posting invalid data via the ODATA API I get the generic http 400 error, bad request!
Well, the data is invalid so I guess it is a bad request but how can I find out what the API is objecting to?
I don't see a meaningful error so it is impossible to diagnose what is wrong; I don't need my data corrected I just need to know how to trap and detect the error so I can deal with errors as they arise.
That is tough indeed. You may want to debug via Fiddler to see if something does show up. Or you import the data in smaller batches until you find the wrong entry?
Thanks Marco, but that is really my question...
How can I trap the error in code? By returning HTTP error 400 I don't get an error message.
I will be transferring thousands of customers and invoices across, surely I can sit there passing them field by field until I find where it goes wrong?
As it happens with my test it was because there was text in a phone number; why return error 400?
Why not return a status code with an error message so we can report it? Saying bad request for the reason above is just weird!
How does anyone manage this?
Sorry but getting frustrated with this API it is the worst one I have ever tried to use.
The following may help and discusses the usage of Fiddler. Yes, if you do have thousands of records to update, the Fiddler trace may become very huge. So limiting the data would be first step.
We currently do not have dedicated Dev support via the Dynamics 365 Business Central forums, but I wanted to provide you some additional resources to assist. If you need assistance with debugging or coding I would recommend discussing this on one of our communities.
I will open this up to the community in case they have something to add.
Thanks for links Marco but I have been trying to join those forums all weekend, I never get the confirmation email from them; not in my junk or our spam filters!
Tried a few other also same thing which is weird!
Is there any useful documentation anywhere; preferably with working examples and ideally downloadable projects?
My boss is keen on moving to Dynamics and I want to help him but I am close to giving up and recommending we look for something better supported...
I have resoled above issue.
The problem was in your User has no proper on DEV server Authentication.
IN SAP Side SAP has not allow that user to update any information.
I was facing that issue on 320 client and 320 *** was not editable.
I have done changes on Editable client and transfer to 320 Non-editable client.
also One More Solution is That.
Clear Your Browser & SAP Side Cash
T-code. Then enter /UI2/PAGE_CACHE_RESET
click on Execute.
Thank you for sharing final solution!
Business Applications communities