The safest thing to capture the value of the field before the bundle update occurred is to create as script that will capture the values and manually execute this before running the said bundle process.

How about consider including ‘role’ to your parameter?

Authorization: OAuth realm=”1234567″, role=”45678″, oauth_consumer_key=”60712990bc09623786e7047c226bcb3f86d49dca0b04efc21001dc76d97a81f5″, oauth_nonce=”bUvpxBX93OWo0FLswq5M”, oauth_timestamp=”1575998103″, oauth_signature_method=”HMAC-SHA256″, oauth_version=”1.0″, oauth_callback=”https%3A%2F%2Fmy.example.com%2FTBA%2F%3FcallbackRequest”, oauth_signature=”7kgwwmiAylqeMdHjCBnIUUW%2BdrDrGCbZGBkuCt39J90%3D”

I believe that you’re missing the oauth_token here. Also, may we confirm if you are using OAuth 2.0 since you have there a oauth_callback

Hello,

It’s because the field has no header name on it since its a custom one. Therefore, you must set an alias on it before calling it directly to the table.

{
"q": "SELECT id, custitem_psgss_material as pggs_materials FROM Item"
}