Sage CRM is a system that controls its user interface using settings contained in the database. The database doesn't just hold the information about the contacts, companies, tasks and opportunities that are vital to the business, it also holds data that describes the lists and screens that the user sees.
The interface could have been written in code, with every field and button being dragged by a programmer from a toolbox onto a web form that crafted in a visual development environment. And every field and button could have had their behaviour written in a piece of code. But it wasn't made like that.
Sage CRM has separated the code that knows how to draw a button, or a field, or a screen from the properties that define the name of the button, the data the field should display, the field that screen should contain.
The data that describes Sage CRM's interface, workflow and business rules is called Meta Data.
Meta Data is probably the most important concept that we need to understand about configuring and developing with Sage CRM.
If we understand how Meta Data is used by Sage CRM to define the properties of screens, lists, menus and business rules like workflow, then we will be far more confident in our ability to configure and customize a system around a customers needs.
Meta Data and Entities
- What makes an Entity?
- Customizing a Screen
- How does Metadata create a Screen?
- Metadata and Screens
- What is a Block in Sage CRM?
- Sage CRM and Referential Integrity
Understanding Metadata in a Customized System
How Metadata controls features
Examples of Metadata controlling Access to 3rd Party Databases
Why Meta Data should only be changed through the Administration screens
Practical usage of Metadata Control
- Custom_Edits and Derived Fields Created in Views
- Adding Derived Fields in Views into Metadata
- The Programmatic Refresh of Meta Data using COM ASP API
Programming without Meta Data