rm_metadataToken is empty string when getting rmclassifications on a node

Guy Walker · 2023-11-03T14:27:02+00:00

There was an error rendering this rich post.

Content Server 22.1, build 16.2.19.1809

ultimatly I'm trying to use DEL: /api/v1/{id}/rmclassifications/{classid}?rm_metadataToken={token}

However, when using GET: /api/v1/{id}/rmclassifications to get the classifications and rm_metadataToken, the rm_metadataToken is returning as an empty string.

this is stopping me from actually doing the delete as without that token I get

what am I missing?

thanks

Guy

Find more posts tagged with

API

xECM

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

Guy Walker

Edit:

what I've noticed is if I remove an RM classification using the browser, I then get a token from the GET request…..

Greg Griffiths

have you logged this with OT support ? are you patched up to date ?

Guy Walker

Hi @Greg Griffiths - I'm assuming so, it's a newish customer system on cloud.

I have worked it out anyway through trial and error. Turns out you don't need this token in all requests. So I wrote some loop that:

GET the RM Classifications

parse the JSON into a list of classification ids, is_primary and the rm_metadataToken value

search the list for any is_primary = false

if none-primary classification found

==⇒ call the DELETE method either with or without the rm_metadataToken depending on whether it came with the GET

else

==⇒ search the list for is_primary = true

==⇒ call the DELETE method either with or without the rm_metadataToken depending on whether it came with the GET

loop while there are classifications

In essance, I remove anything none-primary first, then the primary one. I supply the rm_metadaToken only if the GET returned one.

I am crossing my fingers as this seems to be working.