QuickBooks-V3-DotNET-SDK
QuickBooks-V3-DotNET-SDK copied to clipboard
intuit
More detailed exceptions
I am using the SDK in a .NET 6.0 project. When I call the API to add or update an entity in QuickBooks and there is a validation error (for example a missing account reference), the SDK throws an Intuit.Ipp.Exception.IdsException with Message "BadRequest", that's it! It will be nice to also include details about what is missing. I noticed that this is available in .NET classic versions like .NET 4.5.
Thanks @tjoubert for the feedback... will try to include in the next releases
We support .Net 6.1, 7.2 n .net standard for this sdk. The inner exception should have all the details and otherwise, you can check the readme for enabling logs for the SDK. That has all the details
We support .Net 6.1, 7.2 n .net standard for this sdk. The inner exception should have all the details and otherwise, you can check the readme for enabling logs for the SDK. That has all the details
There is no InnerException on the IdsException object. It may be true that enabling logs would report the details, but I need to report the issue to the individual user at the point of pushing data to QuickBooks Online. So I need it at that time, not being lost in some server-side hidden log file somewhere.
We support .Net 6.1, 7.2 n .net standard for this sdk. The inner exception should have all the details and otherwise, you can check the readme for enabling logs for the SDK. That has all the details
You are wrong to close this issue. Please solve it before you do.
We support .Net 6.1, 7.2 n .net standard for this sdk. The inner exception should have all the details and otherwise, you can check the readme for enabling logs for the SDK. That has all the details
You are wrong to close this issue. Please solve it before you do.
I've just run it again. In NET 4.5, there is the InnerException object on the IdsException, but it's not present in. NET 6.0.
The idsexception has all the details although a bit buried. @rkasaraneni20 can find the right details for you but here is what I have from some other old files I had for a similar issue.
Were your old files running .NET 6.0? I doubt it!
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: nimisha shrivastava @.> Sent: Thursday, February 10, 2022 3:43:01 AM To: intuit/QuickBooks-V3-DotNET-SDK @.> Cc: Terence Joubert @.>; Mention @.> Subject: Re: [intuit/QuickBooks-V3-DotNET-SDK] More detailed exceptions (Issue #220)
The idsexception has all the details although a bit buried. @rkasaraneni20https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frkasaraneni20&data=04%7C01%7C%7C9cb0738f5610406e601108d9ec25e96f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637800469837886172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=SHHjbb43Bct6CHLcfAqZuGAnMTIfZ1su%2FDl7NCDvf80%3D&reserved=0 can find the right details for you but here is what I have from some other old files I had for a similar issue.
— Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fintuit%2FQuickBooks-V3-DotNET-SDK%2Fissues%2F220%23issuecomment-1034320123&data=04%7C01%7C%7C9cb0738f5610406e601108d9ec25e96f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637800469837886172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=xDPYNOs3fI3AyT9AVfB8warK5rd4j1bwc07airCrt24%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABYBBLW4KKJGLLDTWMTONXTU2L3YLANCNFSM5N5LMP7Q&data=04%7C01%7C%7C9cb0738f5610406e601108d9ec25e96f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637800469837886172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=WyIKLl%2BeTu8SqbHBhANum1X2qqLHQjTBLbhHCi7xbn4%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
@tjoubert Our solution is on .NET Standard 2.0 and we support all the samples and in-depth error detailing which are supported with this framework. Based on Microsoft release notes, .NET 6.0 is supported from .NET Standard 2.1. I assume because of this compatibility some of the features might be broken. As of now, we have no plans in pipeline to upgrade to 2.1. Will keep you posted if we plan to migrate or i have any more details