Someone helped me recently with what to put here for the attribute for Part 2. My question is, how do you know what to put here? Do you look up the tables and columns? How can I know how to construct this relationship?
For example, when learning another language I learned grammatical structure, therefore I can gain more understanding about a word and its meaning based upon its construction. In the same way I'm trying to understand where, or how, to learn the language, or the structure, of what to put in these fields? Thank you
For example's sake, let's say you're configuring a field for WOTRACK.XML -- the Work Order Tracking application.
You first have to know the base table that XML form uses; in this case, the WORKORDER table.
Then, if the Attribute you want to add exists and persists in that table, great, just use the Attribute's name (e.g., DESCRIPTION)
But if the Attribute is in a different table, you have to know how that table is related to this table (again, per my example, WORKORDER). Let's suppose I want to add the Asset's Description. So you go to the Database Configuration application, open this table (WORKORDER), and click on the Relationships tab. Search through them until you find the correct relationship to the Child table. In this example, I could filter the Relationships table window for Child Table = ASSET.
As is the case here, sometimes there are multiple Relationships to that Child Table. Read & think through which one is best for the situation. Here, just the plain ol' ASSET relationship is what I need.
So when configuring that field in Application Designer, the attribute would be RELATIONSHIPNAME-DOT-ATTRIBUTENAME. In this example, we would use ASSET.DESCRIPTION (since ASSET is the Relationship Name, then a dot, then the name of the Attribute in the Child Table, which also happens to be ASSET).
Now let's get crazy! You can keep chaining these by dots. Suppose you needed to add the Name/Description of the Asset's Vendor to your form. You'd need a Relationship from WORKORDER to ASSET (which we've already covered), and then from ASSET to COMPANIES.
The answer here would be ASSET.COMPANIES.NAME
So that's starting at the WORKORDER object because that's our form's basis, utilizing a relationship to the Asset table called ASSET, which then utilizes a Relationship from the Asset table to the Companies table called COMPANIES, and then retrieves the value from the NAME attribute in the Companies table.
The form of the relationship name is <RELNAME>.<FIELDNAME> OR <RELNAME>.<RELNAME>.<FIELDNAME>, etc... OR :<RELNAME>.<FIELDNAME> OR <RELNAME>.<RELNAME>.<FIELDNAME>. Please note that the difference above is subtle. For fields within an application, they do not have a semicolon whereas when creating a relationship they do have a semicolon. The using a semicolon also applies to Workflow and communication templates.
Steps to complete:
Unless you want the user to be able to edit the data, please make the field read-only.
3815 Harrison AvenueCincinnati, OH firstname.lastname@example.org
Delivering Maximo as a ServiceLearn More