Understanding Uniface Component Data Structure

✨ This blog post was created with AI assistance to help explain Uniface concepts in a clear and simple way.

📊 What is a Component Data Structure?

In Uniface 10.4, every component has a data structure that acts like a blueprint 🗺️. This blueprint defines which entities (think of them as database tables) and fields (the columns in those tables) your component can work with. It also shows how these entities relate to each other and how to access the data.

The data structure is not just about organizing information—it also controls how your application validates data. For example, it helps enforce referential integrity constraints, which means ensuring that relationships between data remain consistent.

🔗 Related and Nested Entities

When two entities in your component have a relationship, the data structure must reflect this by nesting one entity inside the other. Let's look at a practical example:

Imagine you're building an employee management system. You have employees (PERSON.ORG entity) who work in departments (DEPARTMENT.ORG entity). Since each employee belongs to a department, you would nest the PERSON entity inside the DEPARTMENT entity in your component structure.

📝 Example Structure:

    DEPARTMENT.ORG (parent)
    └── PERSON.ORG (child)
    └── UBUTTONDEF.U (UI buttons)

In this example, UBUTTONDEF.U is a non-database entity used for user interface elements like "Save" and "Delete" buttons.

🎯 The Active Path: Your Data's Journey

The active path is a crucial concept in Uniface. Think of it as the route that your data takes through the component during operations. It determines:

⚡ The order in which triggers fire
🔄 The sequence for retrieving, storing, and deleting data
⌨️ The tab navigation order in forms

The active path follows the structure you've defined. For instance, in our employee example, the system would first process the DEPARTMENT entity, then move to the nested PERSON entity.

🖼️ How to Define Your Structure

The way you define the data structure depends on your component type:

For Forms and Reports 📋

You define the structure visually by drawing entities in the Define Frames worksheet. The layout you create in the designer directly reflects the data structure. This makes it intuitive—what you see is what you get!

For Other Components ⚙️

Use the Define Structure worksheet to explicitly define the relationships and hierarchy of your entities.

💡 Why Does This Matter?

Understanding the component data structure helps you:

✅ Design better applications with proper data relationships
🛡️ Ensure data integrity automatically
🚀 Write less ProcScript code by leveraging default behaviors
🐛 Debug more easily by understanding data flow

🎓 Best Practices

When working with component data structures:

🔍 Always model relationships that exist in your database
📐 Keep the structure as simple as possible
🎯 Use the implicit behavior whenever you can—override with ProcScript only when necessary
📖 Document complex structures for your team

🎬 Conclusion

The component data structure is the foundation of how your Uniface application handles data. By properly defining entity relationships and understanding the active path, you can build more robust applications with less code. Remember: a well-designed structure does much of the heavy lifting for you! 💪

Whether you're building forms, reports, or services, taking time to plan your component data structure will pay dividends throughout your development process.

Happy coding! 🚀

DEV Community