Page Comparison

...

1. Owner Configuration: Owner Currencies which your organization supports
   Must match values in Salesforce (the Salesforce configuration process steps can be found under the 'Salesforce (Pre App Installation Process)' section below) 
   
   
   
   
2. Regional Settings: Countries (country and state relationships, city is optional)
   Must match values in Salesforce (the Salesforce configuration process steps can be found under the 'Salesforce (Pre App Installation Process)' section below) 
   
   
   
   
3. Accounts: Contact Types and Contact Points
   
   
   1. Add an additional contact point to each contact type
      • Name = sfdcid
      • Data Type = Text
      • Allow Multiple = False
      • Required = False
        
        
4. Accounts: Account Status Types
   
   
   
5. Accounts: Account Types
   Must match values setup under the Salesforce Account "Type" field (the Salesforce configuration process steps can be found under the 'Salesforce (Pre App Installation Process)' section below) 
   
   
   
   
6. Billing: Bill Groups
   
   
   
7. Dunning Process: AR Terms
   
   
   
8. Custom Fields
   
   
   1. 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.
   
   

   1. 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

   Note: any additional custom fields setup on package frequencies will not sync to Salesforce
   
   

9. 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
       
       
10. 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

...

1. Navigate to the LogiSense Integration tab within Salesforce
2. Click on the Edit button in the top right
3. Enter the LogiSense instance URL in the Endpoint URL field. This should be the same one you entered in Remote Settings
4. Client Id value should be: 044b8ad6006845c29446b2f18e5b5909
5. For Username and Password enter: admin
6. Click Test Connection button
7. Once you receive a Success response, click Save

...