{% set baseFontFamily = "Roboto" %} /* Add the font family you wish to use. You may need to import it above. */

{% set headerFontFamily = "Montserrat" %} /* This affects only headers on the site. Add the font family you wish to use. You may need to import it above. */

{% set textColor = "#565656" %} /* This sets the universal color of dark text on the site */

{% set pageCenter = "1100px" %} /* This sets the width of the website */

{% set headerType = "fixed" %} /* To make this a fixed header, change the value to "fixed" - otherwise, set it to "static" */

{% set lightGreyColor = "#f7f7f7" %} /* This affects all grey background sections */

{% set baseFontWeight = "normal" %} /* More than likely, you will use one of these values (higher = bolder): 300, 400, 700, 900 */

{% set headerFontWeight = "bold" %} /* For Headers; More than likely, you will use one of these values (higher = bolder): 300, 400, 700, 900 */

{% set buttonRadius = '40px' %} /* "0" for square edges, "10px" for rounded edges, "40px" for pill shape; This will change all buttons */

After you have updated your stylesheet, make sure you turn this module off

Importing Custom Fields From QuickBooks to SalesPad ERP

by salespad on October 14, 2014

workflow rules - sequence matters.jpg

The ability for a user to easily extend functionality for a business solution is always handy. SalesPad ERP offers several means of extending functionality, with the easiest means being User Defined Fields, or UDFs.

UDFs are SalesPad’s version of custom fields in QuickBooks, but with an unlimited number.

Of course you have always been able to create user defined fields in SalesPad ERP, but wouldn’t it be nice if you could just import all the custom data from QuickBooks into SalesPad ERP User Defined Fields? Well, now you can.

Custom Field imports into SalesPad ERP require a very specific setup; this is to ensure that no data is lost in the transfer of information from QuickBooks to SalesPad ERP.

The picture below shows the required setup for a user defined field that is intended to map to the custom field Ship Method in Quickbooks. The field name must match the label of the custom field exactly, with spaces replaced by underscores. The data type must be a variable character field (or varchar) since all custom
fields in QuickBooks are actually stored as strings, regardless of the format.

Finally, the length must be 30 in order to match the max length of custom fields.

Remember that custom fields in QuickBooks propagate down to other business objects. For example, if a customer has a custom field “Ship Method,” that custom field will be available on Sales Documents; however, in ERP, if you want that user defined field to be available on Sales Documents, you must create that one as well, with the same name and matching details as the user defined field on the customer.

With just a little setup time and an integration, you can have all of your custom information from QuickBooks in SalesPad ERP!

Matthew Gritters

Topics: SalesPad Insights

Get Blog Updates

Recent Posts

Popular Posts