Hi All, Has anyone ever seen a response similar to the below when running a SuiteQl query via the REST SuiteTalk API web service (POST /services/rest/query/v1/suiteql HTTP/1.1):

{

"type": "<https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.1>",

"title": "Bad Request",

"status": 400,

"o:errorDetails": [

{

"detail": "Invalid search query. Detailed unprocessed description follows. Search error occurred: Field 'subsidiary' for record 'transaction' was not found. Reason: NOT_EXPOSED - Field is marked as internal for channel SEARCH\nField 'taxtotal' for record 'transaction' was not found. Reason: REMOVED - Field is removed\nField 'total' for record 'transaction' was not found. Reason: NOT_EXPOSED - Field is marked as internal for channel SEARCH\n.",

"o:errorQueryParam": "q",

"o:errorCode": "INVALID_PARAMETER"

}

]

}

I cannot work out why a core field like subsidiary on transaction would suddenly be unavailable via the search channel! Thanks.

Yep, we're struggling with this as well

Hi @Simon We are confused about why we're suddenly seeing this error on certain NS instances, our suspicions are: 1. A certain bit of NS config means these fields become unavailable in search 2. A certain NS upgrade / patch has caused this validation to suddenly apply The method we've found to solve it is by omitting the field named from the search/query, possibly retrieving it from the [main] transaction line instead (e.g. subsidiary from main transaction line does work).

Our understanding is there was an E-Fix that went out this week that made the field

subsidiary

private on the Customer and Transaction table. A support case was raised and it sounds like it's a known defect they're working on addressing.

Raise another ticket with 1 severity and tell them it is impactful to revenue and business operations

We did and there is apparently a fix in progress.