REST: Allow entity identifiers in structure of consumed REST service

On our radar
For some reason, when selecting the data type for an attribute of the structure of a consumed REST service only allows basic types, entities and structures. This means I can't easily use static entities for types I know to be enumerated without casting back-and-forth all the time, and worse, I can't use ListAppend and ListAppendAll because no functions are available in the conversion section, not even built-in ones like TextToEntityRefText :(.

So, I would really really really want the platform to support identifiers as type of an attribute in a structure of a consumed REST service.
Created on 27 Nov 2015
Comments (1)

Luckily, the mapping now fully supports full Expressions, so most problems I had with this are gone now, but I still like this to be implemented (in fact, I encountered this yesterday again).