Some backend access involves large data structures. For example, SAP IDocs or OData entities include many fields you may not need in your service. A good approach in this case is to simplify the data structure and to proceed in your process with the simplified structure.
ODataAdapter_LargeMappings_Example
Click here to download a simple example model that shows how to handle large data structures in Scheer PAS Designer.
Simplifying the Data Structure
The example shows a list of all ordered items for a selected customer. The OrderDetails class of the NorthwindDatabase connector includes all data on an ordered item. To display some data of each ordered item, not all properties of OrderDetails are relevant. You can simplify it to a better structure using a mapping diagram:
The example creates a class OrderDetailsSimplified containing only the ordered item information needed for your service. The mapping diagram above shows how to extract relevant data from the complex structure.
From now on, use the simplified structure in your process implementation. Subsequent steps avoid large data structures with irrelevant properties. This makes mapping diagrams easier to handle by keeping them smaller.
Related Content
Related Documentation: