You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a failed Query goes to Quickbase and we get a unsuccessful query, we got null for the error response. Basically QB returned 0 results but the status code was 200.
How to Reproduce
Create a request that you know will return 0 results in Quickbase.
// Let' say this query will fail and isSuccess will be falsevar(response,errorResponse,isSuccess)=awaitquickbaseClient.QueryRecords(qbQuery);// errorResponse is null! So then this will almost act like a succesful query! not good...
The text was updated successfully, but these errors were encountered:
…Client (#2)
- Modify the QueryRecords method to handle different types of errors more explicitly, including client errors, server errors, and generic failures.
- Introduce additional checks for empty data in the QueryRecords method, returning a specific 'NotFound' error if no records are found.
- Update InsertRecords and UpdateRecords methods for consistent error handling and response processing.
- Improve overall readability and maintainability of the QuickbaseClient class.
NOTE: These changes may affect how client errors and empty query results are handled, requiring adjustments in client code.
Issue
When a failed Query goes to Quickbase and we get a unsuccessful query, we got null for the error response. Basically QB returned 0 results but the status code was 200.
How to Reproduce
Create a request that you know will return 0 results in Quickbase.
Then try to use it like normal.
The text was updated successfully, but these errors were encountered: