I’m trying to use /asset/attributes to write an attribute value (I plan to update multiple at once, but I’m starting small) and even if my service user has full read and write access, I still get an INSUFFICIENT_ACCESS failure:
Am I using this correctly? It seems pretty intuitive… I assume id is that of the asset and name is that of the asset’s attribute, which I’m trying to set to the number specified by value. Does that look right?
Thanks for the reply. Perhaps when creating attributes, there could be some guidance if you don’t follow the convention, with a suggestion of how to fix it?
By the way, whilst the new, edited title does now relate to the root cause, it no longer reflects the issue I was having. I wonder if it will make it harder for others with the same issue to find this thread. When searching for solutions to the problem I was having, if I’d seen a thread called “Attribute naming camel case vs sentence case”, I would almost certainly have ignored it as it sounds unrelated!