Difference between revisions of "Common:Object Construction"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 21: | Line 21: | ||
#*: For example: One ''Order'' can have many ''Tags'', and one ''Tag'' can be applied to many ''Orders''. | #*: For example: One ''Order'' can have many ''Tags'', and one ''Tag'' can be applied to many ''Orders''. | ||
#: | #: | ||
:The objects are now connected by [[Lookup]] fields, which will have names like "related_to_Orders". |
Revision as of 20:58, 22 October 2012
- Click [Define Fields]
- Define up to 10 fields, to get started. (You can add more later.) For each field, specify:
- Field Label - The label users will see
- Internal Field Name - The internal reference name. (Created for you. Modifiable, but generally best left alone.)
- Field Type - Pick one of the many choices
- Follow the prompts to add additional information, depending on the field type.
- When done defining fields, click [Save]
To add additional objects, click [Add an Object] and repeat the process.
Next, establish relationships between the application objects:
- Click [Add a Relationship]
- Under Relationships select the objects to fill in the blanks:
- Between __{baseObject}__ and __{relatedObject}__
- Specify the Relationship Type:
- One to Many - One {baseObject} record can be related to many {relatedObject} records
- For example: One Order can have many OrderItems.
- Many to Many - One {baseObject} record can be related to many {relatedObject} records, and each of the {relatedObject} records can be related to many {baseObject} records
- For example: One Order can have many Tags, and one Tag can be applied to many Orders.
- One to Many - One {baseObject} record can be related to many {relatedObject} records
- The objects are now connected by Lookup fields, which will have names like "related_to_Orders".