Social Enterprise meet ERP…
Frizby is built 100% native to Salesforce.com and provides functionality to extend CRM by providing rich order & operations management post opportunity.

Setup instructions:

Please follow the setup instructions when you add this connector to your Slyncy instance.

Additional instructions:

Requirements

The Salesforce API must be enabled.
Standard contact and account fields that are set to ‘Hidden’ can cause problems. To check this, sign in to your Salesforce account > click on ‘Setup’ > click on ‘App Setup’(left menu) > click on ‘Customize’ > cick on ‘Contacts’ > click on ‘Fields’. Click on the field name, and you will be taken to the Field Information screen for that particular field. Click on ‘Set Field-Level Security’ button, and make sure ‘Visible’ check box is ticked for your profile.
Make sure IP restrictions will allow the server to access your account. This can be set in Setup > Security settings and under Administration Setup cick Network Settings.
Session IP restrictions must be disabled: sessions can be restricted to a particular IP address, so that any other requests would not be valid unless they are from the same IP address which initiated the session. Go to Setup > Security settings and under Administration Setup cick Session Settings.

Frizby Setup

The following field validations must be disabled in Frizby:

Items:

‘Product’ Items must have ‘I Buy This Item’ enabled
Inventory Items must have “I Buy This Item” selected
You cannot specify “I Buy This Item” and “Virtual Item” at the same time
The template data from Frizby may need to be cleared out – unless you want to do a manual migration (see the Integrating Existing Data on VillageChief Sync document). The financial accounts, for example, don’t have a ledger code and won’t match up to any accounts from your financial software package (MYOB, Saasu, etc).
Frizby default Tax Codes: Should be renamed to the default tax code from your accounting system, that way they will sync up. You should do this before syncing anything.

Frizby

Requirements

The Salesforce API must be enabled.
Standard contact and account fields that are set to ‘Hidden’ can cause problems. To check this, sign in to your Salesforce account > click on ‘Setup’ > click on ‘App Setup’(left menu) > click on ‘Customize’ > cick on ‘Contacts’ > click on ‘Fields’. Click on the field name, and you will be taken to the Field Information screen for that particular field. Click on ‘Set Field-Level Security’ button, and make sure ‘Visible’ check box is ticked for your profile.
Make sure IP restrictions will allow the server to access your account. This can be set in Setup > Security settings and under Administration Setup cick Network Settings.
Session IP restrictions must be disabled: sessions can be restricted to a particular IP address, so that any other requests would not be valid unless they are from the same IP address which initiated the session. Go to Setup > Security settings and under Administration Setup cick Session Settings.

Frizby Setup

The following field validations must be disabled in Frizby:

Items:

‘Product’ Items must have ‘I Buy This Item’ enabled
Inventory Items must have “I Buy This Item” selected
You cannot specify “I Buy This Item” and “Virtual Item” at the same time
The template data from Frizby may need to be cleared out – unless you want to do a manual migration (see the Integrating Existing Data on VillageChief Sync document). The financial accounts, for example, don’t have a ledger code and won’t match up to any accounts from your financial software package (MYOB, Saasu, etc).
Frizby default Tax Codes: Should be renamed to the default tax code from your accounting system, that way they will sync up. You should do this before syncing anything.

Notes

Product Long Name support Long name support can be enabled for products. This will use the alternate long name field. You will need to display this on the product page to see the data. A shortened name will be put in the normal field, but changes won't be tranferred back when this option is enabled.

Parties Salesforce stores Contacts and Accounts in seperate tables, and this can cause a bit of a disconnect with systems which use a single table (that's why we call them Parties, because a party is neither a person or a company/account). To complicate things, accounts can not be used in place of contacts for things like supplier codes, invoice contacts, etc. The way we work around this is that parties which are marked as supplier or customers are transferred to the contacts table as well - so if a party is an account (the 'Is Individual' flag is false - which often is determined by other systems as whether the contact has a first name), then it is transferred into the Contacts and Accounts table.

Note that this 'auxiliary' contact is not re-synced after the first sync.

Inventory Item Bundles are not currently supported. We can build out support when necessary

Builds are not currently supported. We can build out support when necessary

Browser not supported