Table of Contents
...
- Owner Configuration: Owner Currencies which your organization supports
Must match values in Salesforce (the Salesforce configuration steps can be found under the 'Salesforce (Pre App Installation Process)' section below) - Regional Settings: Countries (country and state relationships, city is optional)
Must match values in Salesforce (the Salesforce configuration steps can be found under the 'Salesforce (Pre App Installation Process)' section below) - Accounts: Contact Types and Contact Points
- Add an additional contact point to each contact type
- Name = : sfdcid
- Data Type = : Text
- Allow Multiple = : False
- Required = : False
- Add an additional contact point to each contact type
- Accounts: Account Status Types
- Accounts: Account Types
Must match values setup under the Salesforce Account "Type" field (the Salesforce configuration steps can be found under the 'Salesforce (Pre App Installation Process)' section below) - Billing: Bill Groups
- Dunning Process: AR Terms
- Custom Fields
- Account:
- Entity = : Account
- Field Type = : String(255)
- Name = : sfdcid
- Column Name = : sfdcid
- Description = : Salesforce Account Id
- Layout = : Account Settings (optional)
If any additional fields are required to be synced to LogiSense during an account sync they should be added as well. Keep in mind when creating custom fields in LogiSense that the column name must match the Salesforce's native or custom field's API name.
- Package Frequency:
- Entity = : Package Frequency Must match values in Salesforce (Product "Product Family" field)
- Field Type = : String(255)
- List = : True
- Lookup = : False
- Allow Multiple Selection = : False
- Name = : Product Family
- Column Name = : family
- Description = : Salesforce Product Family
- Layout = Package Frequency
- List Values: add the values listed in Salesforce (Setup → Object Manager → Product → Fields & Relationships → Product Family Picklist Values)
- Layout: Package Frequency
Note: any additional custom fields setup on package frequencies will not sync to Salesforce
- Account:
- Packages
- Only packages / package frequencies that are "Active" will be synced to Salesforce
- IMPORTANT!
- A product will be created in Salesforce for each Package Frequency
- The product's name will be constructed by concatenating the following LogiSense fields, "PackageName PackageFrequencyName CurencyCode". For example, "ABC 1m GBP". It is important that all stakeholders are aware of this naming convention so that the names given to packages are user friendly for both Salesforce reps and LogiSense Billing Admins
- If a package was already synced to Salesforce and then becomes inactive on the LogiSense side and resynced, it will be disabled on the Salesforce side and not available to be added to opportunities
- Any package services whose Status pricing is NULL will not be synced to Salesforce
- Rate plans (if applicable) must be attached at the package service level
- Contracts (if applicable) must be attached to the package frequency
- There should be a value in the SKU field. This field is mapped to the Product Code native field on the Product object in Salesforce. When a product is added to an opportunity a unique LogiSense Package Product Code will be assign to the opportunity product (SKU-ID). For example, if the SKU was ABC the product code will become, ABC-1. The next product added to any opportunity would be "SKU"-2, and so on. If no SKU is provided in LogiSense Billing and the product catalog is synced with Salesforce, then the product code for each product added to an opportunity would become, -1, -2, -3, ... (no SKU prefix).
- Select the correct Product Family custom field value on the package frequency
- The current Salesforce app doesn't support tiered pricing. The package will be synced however the tiered structure will not be displayed in Salesforce
- IMPORTANT!
- Only packages / package frequencies that are "Active" will be synced to Salesforce
- Optional Configuration depending on deployment
- Product Catalog Contracts - these can be attached to package frequencies and will be shown on the Salesforce Product Object. (Custom Field: "Minimum Term", LogiSense_Minimum_Term__c)
- Usage Buckets - these can be attached to services and populate the Usage Bucket custom object installed with the Salesforce App. The connection between the usage bucket and service will also be established in Salesforce and show as a read-only "allowance" on the custom Opportunity Product Service Visual Force page
- Rate Plans - standard configuration of Rate Plan/Rate Group/Rates. These must be attached to Package Services and not Package Frequencies in order to allow Salesforce users to override rate amounts
...
- Navigate to the LogiSense Integration tab within Salesforce
- Click on the Edit button in the top right
- Enter the LogiSense instance URL in the Endpoint URL field. This should be the same one you entered in Remote Settings
- Set the Client Id value to: 044b8ad6006845c29446b2f18e5b5909
- For User Name and Password enter the LogiSense Billing credentials supplied by LogiSense
- Click the Test Connection button
- Once you receive a Success response, click Save
...
Additional native or custom fields from the Account object in Salesforce can be mapped in order to sync with LogiSense during account pushBilling when account data is pushed (account data is only pushed down from Salesforce, it is not pulled or pushed from LogiSense Billing).
To configure account field mapping:
- Navigate to the LogiSense Integration tab
- Click on the Account Extensions buttonSelect the
- Salesforce Click the Add Mapping button
- Select the Salesforce Field
- Enter the LogiSense Field value
- Value entered in the column 'Column Name' field for this the custom field on the account Account entity in LogiSense Billing
- This value cannot have spaces and must start with a lowercase letter (Note: even if the Column Name starts with a Capital in the LogiSense Billing UI, the API name will be created with a lowercase letter
- character)
- Continue steps 3-5 above for each field mapping
- Click Save
Package Field Mapping
LogiSense Package Frequency custom fields can be mapped to any custom fields created on the native Salesforce Product object.
...
To configure package frequency to product field mapping:
- Navigate to the LogiSense Integration tab
- Click on the Product Extensions button
- Click the Add Mapping button
- Enter the LogiSense Field value
- Value entered in the
- 'Column Name' field for
- the custom field on the
- Package Frequency entity in LogiSense Billing
- This value cannot have spaces and must start with a lowercase letter (Note: even if the Column Name starts with a Capital in the LogiSense Billing UI, the API name will be created with a lowercase
- character)
- Select the Salesforce field Field to map to
- Click Add Mapping button
- Continue steps 3-5 above for each field mapping
- Click Save
...
By default the only fields that will sync from a Contact perspective are the nameName, title Title and type Type fields. All other fields require mapping to be configured within Salesforce.
IMPORTANT! All contact points for each contact type must be configured prior to syncing any accounts.
To configure mapping of additional contact data:
- Navigate to the LogiSense Integration tab
- Click on the Contact Point Mapping button
- Select the LogiSense Contact Type from the drop down
- Select the Salesforce field Field for each contact point
- Click Save
- Repeat steps 3-5 above for each contact type
- Once all fields across all types have been configured, click Close
...
Account Invoice List
As part of the default Salesforce for LogiSense app, all account invoices in LogiSense will be reflected back to a custom Visualforce page that can be added to the Account object.
...