Pierre, I think that there is a misunderstanding here: the field was declared as an extension in the scrum component and as a consequence the relation to it should also be there, and Deepak fixed this issue; in fact this fix removed a dependency from the order to the scrum component.
Jacopo On Mar 19, 2015, at 11:18 AM, Pierre Smits <pierre.sm...@gmail.com> wrote: > By the way, now order mgr has an even greater dependency on a special > purpose application. > > Best regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Wed, Mar 18, 2015 at 12:33 PM, Pierre Smits <pierre.sm...@gmail.com> > wrote: > >> Hi Deepak, >> >> That issue shortly after the moment release r13.07.01 came available to >> the public. That release didn't have numerous special purpose components >> incorporated. And made that bug visible. >> >> However, though something is uses at a lower level, we should not have >> something as basic as a parent self reference in an entity-extension in a >> lower level component. Maybe the contributor hadn't thought about that, >> when the component was first conceived and there after completed to its >> current state. >> >> Best regards, >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> >>
