It looks good to have one FK relationship while reviewing entity def found following description. This is by design before proceeding we need to check this.
"Defines a permission available to a security group; there is no FK to SecurityPermission because we want to leave open the possibility of ad-hoc permissions, especially for the Entity Data Maintenance pages which have TONS of permissions" Thanks & Regards -- Deepak Dixit 2018-09-25 14:21 GMT+05:30 Jacques Le Roux <[email protected]>: > +1 > > Jacques > > > > Le 24/09/2018 à 08:28, Julien NICOLAS a écrit : > >> +1 >> >> >> Le 22/09/2018 à 14:15, Deepak Nigam a écrit : >> >>> IMO, here the relation type should be 'one' here to maintain >>> the referential integrity. WDYT? >>> >> >> >> >
