QuickBase API Cookbook v3 - Recipe #100
Lookup a field property
lookup field property
Before processing records in some way, you need to know something about the definition of a particular field in QuickBase.
require 'QuickBaseClient'

qbc = QuickBase::Client.new

qbc.getSchema("8emtadvk")
showTimeInDateModified = qbc.lookupFieldPropertyByName("Date Modified","display_time") == "1" ? "is" : "is not"

puts "\nFor the Date Modified field in the QuickBase Community Forum, the time of day #{showTimeInDateModified} displayed.\n"

puts "\nThe field properties you can lookup are: \n\n"
puts qbc.validFieldProperties.join("\n")

=begin

The above code prints -


For the Date Modified field in the QuickBase Community Forum, the time of day is displayed.

The field properties you can lookup are:

allowHTML
allow_new_choices
appears_by_default
append_only
blank_is_zero
bold
carrychoices
comma_start
cover_text
decimal_places
default_kind
default_today
display_dow
display_month
display_relative
display_time
display_today
display_user
display_zone
does_average
does_total
doesdatacopy
exact
find_enabled
foreignkey
label
nowrap
num_lines
required
sort_as_given
unique
use_new_window
target_dbid
target_dbname
target_fieldname
target_fid
source_fieldname
source_fid

=end

lookupFieldPropertyByName.rb
One-Click Ruby Installer for Windows Ruby wrapper for QuickBase HTTP API
Created on March 30, 2008 at  6:25 PM (PDT). Owned by Quick Base.
Quick Base
Show fields from Show fields from Show fields from a related table
Report Name *
Description
Reports and Charts Panel
Each table has a panel listing its reports and charts, organized in groups.
Please wait while your new report is saved...
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.

Read more about converting a column into a table.

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