09-02-22 11:15 AM
09-02-22 12:48 PM
10-02-22 09:15 AM
10-02-22 12:15 PM
10-02-22 01:11 PM
10-02-22 01:25 PM
10-02-22 01:51 PM
10-02-22 02:40 PM
10-02-22 02:56 PM
10-02-22 03:14 PM
Determines the type of data returned, either the actual values from the database or the display values of the fields. Display values are manipulated based on the actual value in the database and user or system settings and preferences.
If returning display values, the value that is returned is dependent on the field type.
- Choice fields: The database value may be a number, but the display value will be more descriptive.
- Date fields: The database value is in UTC format, while the display value is based on the user's time zone.
- Encrypted text: The database value is encrypted, while the displayed value is unencrypted based on the user's encryption context.
Reference fields: The database value is sys_id, but the display value is a display field of the referenced record.
- Data type: String
Valid values:
- true: Returns the display values for all fields.
- false: Returns the actual values from the database.
- all: Returns both actual and display values.
Default: false
If you notice, the default setting of this parameter is false which means it's returning actual database field values. If a field contains binary/hashed/encrypted data, that's what's being returned. You might try setting this field specifically to true and see if that addresses the issue. Otherwise, you can use the sysparm_fields query parameter to specify the list of fields to return (accepts a comma delimited string of field names to return). Start with just one or two fields and see how that works. Then you can add on to it from there.
You said this works fine in Postman. You can also take a look at the specific Postman request and verify what, if any, query params are specified there.
Cheers,