[aidan]

I recently ran into issues when using an integration record with TBA to request for multiple pages of transaction summary records when using the getPostingTransactionSummary web services action.

I found the first request was consistently successful, but following requests for successive pages would fail giving the following error:For pages > 1, search parameters must match the original search exactlyI followed the suggestions in SuiteAnswer 33416 labeled “getPostingTransactionSummary returns an error: For pages > 1, search parameters must match the original search exactly”. I then ensured we were requesting the first page first, ensured no field or filter parameters had changed, and was requesting the second page immediately.

The mechanism used to generate signature appears to be correct as all calls to any web service endpoint for the first page are always successful.

The following represents the sequence of requests used to reproduce (where real data is mocked):

Request for first page:

HTML Code:
    

1234567 12345 1234 62005285 1478114023 NIhrCvTi2SpGfhxbxO8N09WQ7mvXw7oJICiEewCtm1 M=     

                                           true                 true                 true                 true                                                                                                                                                                                                            1              
Response for first page:

HTML Code:

WEBSERVICES_1234

2150 1000 3 1 100 100 …. MORE RECORDS HERE
Request for second page:

HTML Code:
    

1234567 12345 1234 64687129 1478114087 HWQ/O4MSz5L6/TRu0GhtxU37yXIHdhSqvznbG92Salg=     

                                           true                 true                 true                 true                                                                                                                                                                                                            2              
Response for second page:

HTML Code:

WEBSERVICES_1234

USER_ERROR For pages > 1, search parameters must match the original search exactly
The error leads me to suggest that the first request is not cached on netsuite’s side correctly. I have also tried various permutations of fields in the token passport for the second request to no avail.

Any assistance appreciated.
This is a cached copy. Click here to see the original post.

[chanarbon]

Hi aidan,

Are you aware that TBA for WS has the session unique per TBA-based request

[aidan]

Hi chanarbon,

Thank you for the response. Yes and I believe that is likely related to the issue above.

Currently for every call into WS I am regenerating the signature with new nonce and timestamp. This includes calls for successive pages. To be clear I do regenerate signature, nonce and timestamp when requesting for the next page. Considering the only changes between the first and second request are nonce, timestamp, signature and pageIndex that seems to be where the problem lies. Should the tokenPassport be omitted entirely when requesting for the next page?

Thank you

[Author]

Posts