We are updating our Terms of Service.
See our blog post highlighting the changes.
By continuing to use the Quick Base Service, the new Terms of Service will become effective on the renewal date for each account that you manage.
If you do not accept the changes, please notify us thirty days in advance of your renewal date.
- added the ability to generate a single Merged PDF for for multiple records.
- added filename as metadata to the Amazon S3 upload process
- removed requirement of specific input parameters, repository,rlfn,amazons3. These can be omitted if not being used
- added new parameter for detail data table - "noborder". This will suppress the borders from printing for all cells of a detail table.
No value needed, pass it in as is.
- fix issue when "noheader" was being used. the table was not centering in the document properly
- added ability to save the merged pdf file to Amazon S3
- added some validation of parameters in subtable parameter list
- fixed subtotal row issue whe a date column showed in the table. A default date was showing up when subtotalling was requested
- changed the way data is being retrieved in subtables. More efficient data retrieval process now.
- use the clist parameter instead of the default report to determine which columns to return from a query.
- added ability to show a checkbox image when displaying a checkbox field in a document.
- added ability to display images in the detail table of the document.
- change the file naming process so that when generating more than 1 file the user will have more control over the
file name. Pass fn=~3.4.5~ and the file will be named with the values in these fids. If no ~~ are found in the fn parameter then old file name process is used.
- fixed issue related to a text field that contains a "$" character.
- merge pdf process - fixed issue internally when processing individual pdf files. - clean up issue, no user impact
- ability to display images that are not file attachment fields. So it is now possible to display an image if it is referenced in a formula text field with a <img src> tag.
(must us the "I" format parameter with the field id in the clist)
- efficiency changes
- added "clist" as a parameter to the main URL string so if using the msqry parameter you can specify the columns to return within the new clist parameter.
- fixed issue when noheader is being used. A blank row was appearing at the top of the subtable when noheader with a border was being used.
- added 2 new main URL parameters, appid and tpdbid
tpdbid - you can now pass in the dbid of the table that stores the document template files. So you can have multiple tables if you want.
appid - the dbid of the application should be passed in with this parameter.
- fixed issue with merged pdf process when only 1 document was being created. The merged pdf was not being created if only 1 pdf was created. This is now fixed.
- added new parameter so you can control the name of the merged pdf file, "mrgfn"
- changes to handle displaying images for the master record even if they are not in file attachment fields. So if the image file is referenced within a text/html field or in a URL field it will dispaly in the document properly.
- also added the ability to size the images in the master. New format option...~i:fid:200~
(must use the fid and not the field name)
- added s3 parms to the URL so they can be passed in. They are optional, if not passed in then use values from the webconfig (s3key and s3bkt)
- change so if the "Record ID#" field was renamed it can be used with the new field name. Older versions require the Record ID# field as is and now you can use a renamed key field.
- fixed issue with float decimal fields displaying as 2 decimal digits instead of the actual number defined in quickbase
Print the report as a table
Print one revision per page ( total)
Using the form:
Print as much of the timeline as fits on a single page
Print the timeline over multiple letter-size pages in landscape orientation
When you bring additional fields into a conversion, Quick Base 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, Quick Base finds three different locations for Acme. A single value in the column you're converting can only match one value in any additional field. Quick Base 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.