Building Master Detail Associations¶
Associations mean relationship between the Entities. This is required when the user wants to filter the records of the Entity in relation to the Configuring Projection. This is the typical master detail scenario user finds in the application.
In a master details relationship if a list is added to filter out the records depending on Parent Child relationship, then needs to refer to the selector and load the data set.
In below scenario, Person records will be filtered in the added List depending on the selected record in the PersonInfo Selector in the Person Page. User can add data to any “Person” record. But if its required to filter the records to the current “Person” record user is in, then user needs to create a binding between the list and the “Person” Record currently shows in the page. For this Entity Associations can be used. Person Info Selector is the main element which picks up the records for the “Person” Page and all the other elements are based on that.
Configure Aurena Page with Entity Association¶
Under the list that has been added to the content header in the page section, user can add master detail relationship. Add a binding by clicking + icon in front of the Binding field.
Then it will be displayed as below where we can add Bindname and Property. For this scenario bindname is “PersonInfoSelector” (Which is the selector of the page) as it is the main element to pick up records in the page and it will be bound to the Property that has been created which is “Array_ref” (Association created previously. Please refer Entity Associations on projection configurations). Save the configurations and publish.
Now if the user tries to load a person record from the selector, then it will filter out the records in the list according to the loaded Person record.