| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
We're glad you're interested in doing more with Quickbase!
Now we need to make you official before you share apps or manage your account.
Verifying your email lets you share Quickbase with others in your company.
Your work email |
Your company |
| 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:
