Business Model Design with XPO

• Nov 28, 2024
• 2 minutes to read

In XPO, a business model is declared by classes (Persistent Objects) that will define the database structure, and consequently, the user interface. Classes represent database tables and class properties refer to database table columns. You can declare persistent objects directly in code (Code First) or by using the XPO Data Model Designer (Model First), or generate code from an existing database (Database First). The topics in this section provide information on how to properly declare your data classes.

Note

It is recommended that you first review the XPO tutorials to learn about the fundamental XPO concepts before creating an XPO-based XAF application.

Concepts

• Business Classes vs Database Tables
• Ways to Add a Business Class
• Base Persistent Classes
• Relationships Between Persistent Objects
• Optimistic Concurrency Control

XPO Documentation on Relations and Filter Criteria

• Relationships Between Objects
• How to: Build Simple Criteria
• How to: Build Complex Criteria

Task-Based Help

• Generate XPO Business Classes for Existing Data Tables
• Calculate a Property Value Based on Values from a Detail Collection
• Change the Format Used for the FullAddress and FullName Properties
• Create a Business Model in the XPO Data Model Designer
• Implement a Custom Base Persistent Class
• Implement File Data Properties
• Initialize Business Objects with Default Property Values in XPO
• Map a Persistent Class to a Database View Which Has No Key Field
• Recompile the Business Class Library
• Relationships Between Persistent Objects in Code and UI
• Handle Renamings and Deletions of Business Classes and their Properties
• Use XPO Upcasting in XAF
• Auto-Generate Unique Number Sequence

Community Content

• Modifying Business Objects using Attributes
• ORM Magic – Importing from Any Datasource
• Fast prototyping requires an initial data import mechanism
• How to Create an XAF Application from Scratch