Modeling Navigation Properties
By default, the component models Navigation Properties as separate views. The views are named in the format ParentTable_NavigationProperty.
Querying Navigation Properties
For an example of working with a navigation property as a view, the JobApplication entity has a lot of navigation properties. We will look at the "education" navigation property. The CData FireDAC Components for SAP SuccessFactors will display a view called JobApplication_education. Retrieving data from JobApplication_education will display the JobApplicationSnapshot_Education object associated with a given JobApplication. The JobApplication_education view has a primary key made up of the Id of the parent entity and the Id of the related entity.