Suppose I have a data model with Airport->Terminals->Airlines. Airport->Terminal is a composition relationship. Terminal->Airlines is a one-to-many relationship. This implies that an airline can only relate to a single terminal. It isn’t a perfect real world example but let’s go with it. In the attached sample project, I have browser and editor screens for each eantity. The Terminal editor uses a TokenList to seelect the associated Airlines. But every time I create a terminal, whether from the Airport editor or the Terminal browser, and associate airlines to this new terminal, it is trying to double save the new temrinal. I have played with different combinations of views but I cannot figure out how to prevent this from happening. I have some intuition that this is due to the allAirlinesDs and the airlinesDs both including the temrinal attribute into their view. But as I understand it, both need to contain that attribute. Can anyone give some guidance on this?
TestManyToOneTokenList.zip (93.7 KB)