I have a Custom Transaction Body Field

custbody_foo

. Under Access -> Default Level for Search/Reporting, when this is set to

Run

, I'm unable to run a simple

Nsearch.lookupFields({
    type: Nsearch.Type.ESTIMATE,
    id: 23456,
    columns: [ 'custbody_foo' ],
});

as I get error

SSS_INVALID_SRCH_COL

, however if I change the Default Level for Search/Reporting to

Edit

, the above

N/search.lookupFields

works just fine. According to the help for that that field, it indicates that

Run

should be enough.

Choose the level of access you want given by default to this field on reports and search.

• Edit – The field and its contents can be viewed and changed.

• Run – The field can be seen, but its contents cannot be changed.

Am I missing documentation somewhere that indicates Default Level for Search/Reporting =

Run

doesn't work with

N/search.lookupFields

or is this a bug?

idk if I'd call it a bug at this point, its well-known issue, you're not wrong its documented poorly, but i feel like it is mentioned somewhere obscurely that this is the case.... I'm not going to try and find it, it might not have been actual docs i saw maybe someone just told me eons ago 😉

noted. "well-known" issue is good enough for me. First time I ran across it and couldn't find any supporting evidence from googling.