 |
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Profile
Sign up now
Manage 
Sign out- This app
- TPL LandVote Database
- Your role is Outsider
- Switch accounts
-
{{firstServiceAccount.FirstName}} {{firstServiceAccount.LastName}} (Service){{firstServiceAccount.Email}}
-
{{secondServiceAccount.FirstName}} {{secondServiceAccount.LastName}} (Service){{secondServiceAccount.Email}}
-
More accounts
-
{{serviceAccount.FirstName}} {{serviceAccount.LastName}} (Service){{serviceAccount.Email}}
-
| Field label | |
| Column heading override | |
| Justification | |
| What does auto mean? | |
|
|
|
Fields in:
|
|
Fields to Extract: |
|
| Name for the new table: | |
| Items in the new table are called: |
When you bring additional fields into a conversion, Quickbase often finds inconsistencies. For example, say you're converting your Companies column into its own table. One company, Acme Corporation, has offices in New York, Dallas and Portland. So, when you add the City column to the conversion, Quickbase finds three different locations for Acme. A single value in the column you're converting can only match one value in any additional field. Quickbase needs you to clean up the extra cities before it can create your new table. To do so, you have one of two choices:
- If you want to create three separate Acme records (Acme-New York, Acme-Dallas and Acme-Portland) click the Conform link at the top of the column.
- If the dissimilar entries are mistakes (say Acme only has one office in New York and the other locations are data-entry errors) go back into your table and correct the inconsistencies—in this case, changing all locations to New York. Then try the conversion again.