Business Model Design with XPO
- 2 minutes to read
In eXpressPersistent Objects (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
XPO Documentation on Filter Criteria
Task-Based Help
- How to: Generate XPO Business Classes for Existing Data Tables
- How to: Calculate a Property Value Based on Values from a Detail Collection
- How to: Change the Format Used for the FullAddress and FullName Properties
- How to: Create a Business Model in the XPO Data Model Designer
- How to: Implement a Custom Base Persistent Class
- How to: Implement File Data Properties
- How to: Initialize Business Objects with Default Property Values in XPO
- How to: Map a Persistent Class to a Database View Which Has No Key Field
- How to: Recompile the Business Class Library
- Relationships Between Persistent Objects in Code and UI
- How to: Handle Renamings and Deletions of Business Classes and their Properties
- How to: Use XPO Upcasting in XAF
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
See Also