Structure and Records

In what Scenario we should use the Structure and record Data types .Please Provide the use cases.

Note: Please  do not Provide the tutorials as solutions of outsystem.

Hi @Sangam

We Use Structures and Records to create compound Data Types.
I can explain the Structure and Record data type some brief as per my knowledge.


i) When you need to store multiple entity data's or two store temporary purpose till you are hitting the server to store the database. we use structures.

ii) when you need to combine the different entities data like


I'm having an entity of school and having different 10 attributes and another entity College having 8 attributes, But when I want 3 attributes from school and 6 attributes from college just to store purposes or to display purposes I use the Structure.

Regarding Structures I'm attaching one OML, Please find the attachment for your reference If any Queries Please comment or connect through the profile.

Record Data Types

Where we want to find and review places of interest, we want to return basic information about a Place using a REST API method. 

The information to return about each place is the Id, the name, and the average rating. The data is stored in the Place Entity an Review Entity.

The data type that we need to assign to the output parameter will only be used we will use a Record:

Yes, I  won't provide any tutorials, But just go through those or Documentation .

I hope this helps you, If any queries please acknowledge the post or connect from the Outsystems profile, ready to help you.

- Palle Vijay Bhaskar Reddy

Hierarchy Saving.oml


Hello Sangam Bhondele,

(To enrich the topic of the post)

Another example of a use case to use structure, in this case for advanced query, where only some specific fields need to be returned in the query, instead of all the fields of the two tables Order and Client:

Hope it helps.


Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.