Hi Raghu and thanks for the follow up
Yes for a technical side this is reasonable to have the error at the output.
However from the functional side this don't appears sufficient to me. As an MSP you would like that the public references are available to any tenants (look for me to be the purpose to be public).
This is how the behavior is either working on the web interface. Then the REST API is adding an unnecessary limitation here.
In many case single reference is to be shared across (for example to enforce consistency across multiple tenants served by an MSP) vs. to be created multiple time.
This is either worse because let's say you duplicate 2 references with the same name in 2 different tenants you may be at the risk as depending of the creation sequence that because the first id returned by the lookup was created into another tenant that will also have a record not found error.
I was glad to see that you can use COMMON_NAME in the REST_API vs. to have to do multiple call like in SOAP but then get frustrated, by up to my view, an unnecessary limitation. This look like we stopped at only a half of the destination...
My 2 cents
/J