Hey guys! New to the community so apologies if thi...
# suitetalkapi
c
Hey guys! New to the community so apologies if this is the wrong place to ask. I have a SOAP Search that I am sending out, which queries a Saved Search. It's not returning a bunch of fields that I am expecting (or to be clearer - it returns the fields, but not the values of those fields). The fields are all custom fields that our Netsuite Admin has added for us. I checked the documentation and it mentions that this might be caused by the fact that the <searchPreference> bodyFieldsOnly is ignored and set to false for Advanced Searches. These fields and values show up if I do a basicSearch (but it shows ALL the fields, which is not really ideal) Is there any way around that limitation? Or should I consider a different way to get the report I want (not use advanced Searches, and just do two basic searches?)
b
what does your request look like
c
So this is the body and search preferences, the header is just the token based auth stuff
b
that looks like it should return whatever columns on the referenced search
minus any that use features that advanced searches dont support like formulas
c
That is also what I was expecting - but its not returning any value for the fields. Its a weird one - Is there any way to set the searchPreference to return bodyFieldsOnly as true?
b
bodyFieldsOnly is irrelevant, its uses for a basic search to not include sublists
basic debugging is to run the saved search using the same role and user in the ui
to see if you have access to the columns
c
Yup - The search was created by one of our Netsuite admins, and when I run it, I can see the data in the report fine - all fields are populated. Let me see if I can grab the output of the search, and sanitize it then share it here
b
honestly the column definitions are more useful
c
So this is one of the fields - in the Web UI when I run the report, it populates correctly - but this is all it shows (no value) when running
Ah ok - I'll grab that now
Actually - the SOAP user that I use isn't my user - its a different API user. This (I guess) means that I have access to that report, but maybe the API user doesn't - Let me check to see if that is the case. Thanks @battk