Hi, Wixers.
I’m new to using multi-references of collection and have a question. When I define a multi-reference field in the main collection, a reference field is automatically added in the referenced collection. Is this normal behavior of multi reference? When I added reference field (not multi), that’s not happened.
Yes. This is how it works.
By the way the multi-reference field is not part of the collection scheme, and you only see it in the Content Manager. But if you query the collection, the item you retrieve won’t include the multi-reference field values, unlike single-reference.
Thanks to your quick reply, JD.
I found this is normal behavior based on the design of this feature.
So, does it means, unlike the case of defining a single reference field, when defining multiple reference field let the collections be possible to do bidirectionally reference each other? 
Rather, is it designed like this for that reason? Or it means this difference occurs from internal implementation difference between single-reference and multi -reference?
I assume If only refer from one side(main collection), adding fields to the other side seems pointless.
Or simply, the reason why adding a field is to show where the collection being browsed is referenced from?
Also, is it not possible to change the field key (something like maincollectionID-1) of the automatically added multi-reference field?
Does this mean that we have to change only the name of the automatically given fields to distinguish them?
thanks in advance.
See this duiscussion:
Best Answer!! thank you J.D.
I understand that there is no reason to actively use multiple reference fields as long as Velo is available.