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
Problem: When searching accounts with specified columns we see a successful request and response from the SuiteTalk API but the gem does not correctly parse the response. Specifically we create the search result and populate the instance fields here If we get values returned in the search response which we don't have defined as a field on Account we don't populate anything for these.
Repro:
Make an example call like below for a instantiated client.
Assuming results, see that accounts.results.first.name is nil while the Suitetalk XML response does populate this value. accounts.results.first.internal_id is populated because we have special handling see here and here.
This was discovered when improving search performance. This same issue may be applicable to other models within this gem.
The text was updated successfully, but these errors were encountered:
sbudker-stripe
changed the title
Advanced Account search does not parse all response search columns from results
Advanced search column Account search does not parse fields from results
May 22, 2023
Problem: When searching accounts with specified columns we see a successful request and response from the SuiteTalk API but the gem does not correctly parse the response. Specifically we create the search result and populate the instance fields here If we get values returned in the search response which we don't have defined as a field on Account we don't populate anything for these.
Repro:
Make an example call like below for a instantiated client.
Assuming results, see that
accounts.results.first.name
is nil while the Suitetalk XML response does populate this value.accounts.results.first.internal_id
is populated because we have special handling see here and here.Gem version:
0.9.3
SuiteTalk API version:
2018_1
Notes:
The fields defined on the Account model can be named differently than the results from the AccountSearchRowBasic fields.
This was discovered when improving search performance. This same issue may be applicable to other models within this gem.
The text was updated successfully, but these errors were encountered: