REST API documentation vs REST API Explorer

[lucaburgazzoli]

Hello,

Wile developing an external integration application based on REST API, I found out that the documentation and the API Explorer seem to be non in sync, i.e. in Helsinki's documentation about Table API's POST I see 5 fields described:

sysparm_display_value

sysparm_fields

sysparm_view

sysparm_exclude_reference_link

sysparm_input_display_value

Whereas on API Explorer (for the same release of course) I have 6 fields:

sysparm_display_value

sysparm_fields

sysparm_view

sysparm_exclude_reference_link

sysparm_input_display_value

sysparm_suppress_auto_sys_field

Similar issue is for Table API's GET were the API doc lists more parameter that those shown by the explorer: who is the driver ?

Cheers,

Luca

[Chuck Tomasi]

Trust the app. The docs sometimes lag. I'll ping one of our documentation people to let them know. Thanks for bringing this to our attention.

[lucaburgazzoli]

Thank you, there is a significant difference among the two so it is a little bit confusing.  

[Chuck Tomasi]

Message delivered.

[Chuck Tomasi]

Hi Luca,

I received a response. It turns out this is a known PRB with GlideRecordSecure. Our developers believe nobody is using the sysparm_supress_auto_sys_field parameter and are thinking of deprecating it. I highly recommend putting in an incident and referencing

PRB714537

Personally, I know I could have used it about 18 months ago had I known about it. I also feel that any time we remove something without a suitable upgrade path, there is unintended and understandable backlash.

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

If you are viewing this from the community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.

Thank you