About the Copy Master and Detail Records Option

You can add a button to your application that users can click to copy or import records and the relationships between them. Use the Copy Master and Detail Records option to add a Formula- URL field that displays as a button in a specified table that either:

When you create a copy or import button, you specify the master table in which the new Formula -URL field appears, and decide whether all or a subset of detail records are copied, and whether QuickBase should recursively copy all detail records. You also specify the text that appears on the button; make sure you use descriptive text so that users understand what will happen when they click the button.

To access the Copy Master and Detail Records option:

Creating a copy or import button involves:


Understanding how application users use the copy or import button

Before you create a copy or import button, it's helpful to understand how the button appears on your forms and what happens when a user clicks it.

This section contains examples for:

Using a copy button

In this example, a Copy this record button has been added to a form, shown below.


When a user clicks the Copy this record button, a confirmation message opens. The user clicks Go to record on the confirmation message, and the form for the new record opens, shown below.  The name of the new record is prefaced with "Copy of" and the copied detail records have the icon.
top

Using an import button

In this example, an import button has been added to a Project form, shown below.

When a user clicks the Import detail records button, a confirmation message opens, indicating how many records were created. The user clicks Go to Project on the confirmation message, and can see that project's details list now contains seven imported detail records, which indicated with the icon.

top

Understanding the limitations and restrictions for copying and importing records

You should understand the following limitations and restrictions before creating a copy or import button:

top

How QuickBase maps predecessor relationships when it copies or imports records

Records in QuickBase may have predecessor relationships.  For example, tasks in a project usually occur in a specific order and one task cannot start until another task finishes. This means that one task depends on another one. A predecessor task is a task that must finish before another task can begin. When you specify a predecessor for a task, you set up a dependency between two tasks (which is why predecessors are sometimes also called dependencies). A successor task is a task that cannot start until another task finishes. (Read more about predecessors.)

If a detail record contains a predecessor field, QuickBase attempts to map predecessors as follows:

Consider this example of copying master and detail records in a Project Management application, illustrated below. A user copies a master Project record, called "Software Release", with detail Task records 1, 2, 3, 4. The new master record is called "Copy of Software Release" and has detail records 101, 102, 103, 104. The application has another master Project record, called "Product Review", with detail Task records 11 and 12.  QuickBase maps predecessor relationships as follows:

top

 

Related Topics:

 

Return to top   

© 1999-2014   Intuit Inc.  All rights reserved.  Legal Notices.