1. Tutorial One-to-Many DataPages Note: A new and easier way of building one-to-many DataPages is under development, but for now, here’s how you can create great relational apps, without much effort. December 2009
2. End Results One-to-Many Details Page 2 Contact History is a child of Customers table. On the details page Customer’s info is shown plus their Contact History and a web form to submit new Log for this customer.
3. Tables Structure 3 Customers table is primary and CustIDis it’s unique ID field. Call_Logis a the child table and CustIDis the record ID from the parent table. It creates a relationship with the parent table. Note the data types.
4. DataPages in Details Page 4 Three related DataPages will be configured for deployment into a single Details page.
5. Search and Results DataPage – 1 of 4 5 Instead of the standard details page, we pass CustID(Customer ID) to a separate web page where the 3 DataPages are deployed. Search Form Results Page Details Page CustID=x Two screens of a Search and Report DataPage Separate Details page
6. Search and Results DataPage – 2 of 4 6 Enable Advanced Options and Parameters
7. Search and Results DataPage – 3 of 4The Key Step 7 2: See below 3: Insert the ID as a parameter on the link 1. Insert an HTML block Step 2: Enter HTML link to where your details page will be deployed. Link should be in the format pagename.htm?ParamName=[@field:FieldName] In this example we use < a href=“details.htm?CustID=[@field:CustID]”>Details</a> pagename.htm: Page name or extension doesn’t matter, but this is the page where the other 3 DataPages should be deployed in.