9 Messages
•
465 Points
Asset and Attribute API Calls deprecated typeIds (the list)
Noticed in the REST API documentation that the typeIds now say depracated as well as typeId and that there's now typePublicIds.
Did I miss any comms about this?
9 Messages
•
465 Points
Noticed in the REST API documentation that the typeIds now say depracated as well as typeId and that there's now typePublicIds.
Did I miss any comms about this?
tomfriesen
161 Messages
•
550 Points
1 month ago
I saw this, too, in the Java API, and was not impressed.
FWIW, I've always recognized the Collibra API as super-well designed in years past. It's accessible, predictable, and pretty reliable. 👍
Lately, however, I've had some concerns.
First, we had to convert our workflows to accommodate a move from UUIDs to much more error-prone Strings. 🤮 This seemed like a terrible design decision, as workflow developers would always have to explicitly convert the Strings to UUIDs anyway to leverage the API.
But deprecating UUID type specification? This is much, much worse.😱 With hundreds of workflows, this deprecation implies a conversion project that my organization simply would not be able to undertake.
Perhaps someone from Collibra can chime in?
0
0