RELATED IDEAS
Inconsistant REST API
Why does the model for an EntityType and FieldSet not return all the translations for the Name/Description property, but the FieldType and Category do? In a request for creating/updating a EntityType and Fieldset, the API accepts an object with translations for the name/description property. But why is that dictionary not returned in the GET requests? Why does it just return a string for that property?
I would like this inconsistency to be fixed. Because right now, there is no way to fetch translations for the name/description property for an EntityType and FieldSet.
[edited to fit Idea purpose]
-
-
-
-
-
-
-
-
-
-
-
- +1
A maybe minor thing, but why when we GetAllEntityTypes() with the REST API is there a property called FieldTypes, which only contains a string collection of FieldTypeIds, when in the same response object we have another property called FieldSetIds, which ALSO is a string collection of just the ids of field sets.
Based on the naming I'd expect the FieldTypes property to have the actual FieldType objects, rather than just the id of the FieldType...
This inconsistency is a significant issue for us when onboarding new brands into our international Inriver group solution. Since we operate a multi-language setup, missing translations create major challenges and hinder efficient implementation. This needs to be addressed as soon as possible.
This is super frustrating. The Remoting API did/does this properly.
To clarify: All other endpoints related to fieldsets in the REST API correctly use a model where Name and Description are localized. Just not the GET endpoint.
I understand that this could be difficult to change now that people have likely started consuming this endpoint, but perhaps you could provide a new version that implements this change?