...

1. 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) 
   
   
   
   
2. 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) 
   
   
   
   
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 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)
        Image Added
        
        

   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 'Column Name' value 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
        
        
        
      • List Values: add the values listed in Salesforce (Setup → Object Manager → Product → Fields & Relationships → Product Family Picklist Values)
        
        
        
      • Layout: Add to Package Frequency Layout

   Note: any additional custom fields setup on package frequencies will not sync to Salesforce by default, to configure syncing of custom fields see the 'Package Field Mapping' section below
   
   

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

...

There is no mapping screen within Salesforce between LogiSense and Salesforce country/states. Instead , instead the app relies on standard ISO codes. You are covered when it comes to countries, however keep this in mind when configuring states in both systems as the LogiSense Billing States Abbreviation value should match the Salesforce State Code value.

...

1. Activate Multiple Currency Support
   Must match values in LogiSense Owner Currencies
   
   
   1. In Salesforce access Setup
   2. Search for 'Company' on the left and expand Company Settings
   3. Click on Company Information
   4. On the Company Information screen click on the Edit button
   5. Enable Activate Mutliple Currencies
      
      
      
   6. Click Save
   7. On the Company Information screen click the Currency Setup button
   8. On the Currency page ensure that the currencies setup match the LogiSense Billing currencies configured (click New to add additional currencies)
      
      
2. Enable Country State Picklist Support
   Must match values in LogiSense Regional Settings
   
   
   1. In Salesforce access Setup
   2. Search for 'Country' on the left and select the State and Country/Territory Picklists option
      
      
   3. Complete the 'Configure states and countries' step ensuring the states and countries configured in your Salesforce org match the states and countries setup in LogiSense Billing
   4. Complete the 'Scan your organization' step to check for sate/country references
      
   5. Complete the 'Covert your data' step
   6. Turn on state and country/territory picklists by licking the Enable button
      
      
3. Add LogiSense instance URL to Remote Site Settings
   
   1. In Salesforce access Setup
   2. Search for 'Remote' on the left and select Remote Site Settings
   3. Click the New Remote Site button
   4. Enter a name for the site under Remote Site Name
   5. Enter the URL of the LogiSense Billing application under Remote Site URL
   6. Click Save
      
      
4. Configure Product Family Picklist
   Must match values in LogiSense Package Frequency Custom Field "Product Family"
   
   
   1. In Salesforce access the Object Manager
   2. Load Fields & Relationships then select Product Family
   3. Under Product Family Picketlist Values add new values to match the custom field values populated on price frequencies in LogiSense Billing
      
      
5. Configure Account Type Picklist
   Must match values in LogiSense Account Types
   
   
   1. In Salesforce access the Object Manager
   2. Load Fields & Relationships then select Type
   3. Under Account Type Picketlist Values add new values to match the account types setup in LogiSense Billing
      
      
6. Setup Custom Profiles that LogiSense App permissions will be added to (Note: permissions cannot be mapped to stock Salesforce profiles)
   1. in Salesforce access Setup
   2. Load / search for Profiles
   3. Clone the profiles for administrators and agents that will be using the LogiSense App. E.g. if your sales staff are using the 'Standard User' profile, clone that profile (e.g. a cloned profile named 'LogiSense Standard User')
      

...

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. Set the Client Id value to: 044b8ad6006845c29446b2f18e5b5909
5. For User Name and Password enter the LogiSense Billing credentials supplied by LogiSense
6. Click the Test Connection button
7. Once you receive a Success response, click Save

...

Remember that this only works from Salesforce to LogiSense, meaning that if any changes are made to Accounts or Contacts within LogiSense are not pushed to Salesforce. Therefore it is recommended that the Salesforce instance be the master for any Account/Contact updates or hierarchical structure.

Account Field Mapping

Additional native or custom fields from the Account object in Salesforce can be mapped in order to sync with LogiSense Billing when account data is pushed (account data is only pushed down from Salesforce, it is not pulled or pushed from LogiSense Billing).

...

1. Navigate to the LogiSense Integration tab
2. Click on the Account Extensions button
3. Click the Add Mapping button
4. Select the Salesforce Field
5. Enter the LogiSense Field value
   • Value entered in the 'Column Name' field for the custom field on the 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 character)
     
6. Continue steps 3-5 above for each field mapping
7. Click Save

Package Field Mapping

LogiSense Package Frequency custom fields can be mapped to any custom fields created on the native Salesforce Product object.

...

1. each field mapping
2. 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:

1. Navigate to the LogiSense Integration tab
2. Click on the Product Extensions button
3. Click the Add Mapping button
4. Enter the LogiSense Field value
   1. Value entered in the 'Column Name' field for the custom field on the Package Frequency entity in LogiSense Billing
   2. 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)
      
5. Select the Salesforce Field to map to
6. Continue steps 3-5 above for each field mapping
7. Click Save

Contact Field Mapping

By default the only fields that will sync from a Contact perspective are the Name, Title and Type fields. All other fields require mapping to be configured within Salesforce.

...

1. Navigate to the LogiSense Integration tab
2. Click on the Contact Point Mapping button
3. Select the LogiSense Contact Type from the drop down
4. Select the Salesforce Field for each contact point
   Image RemovedImage Added
5. Click Save
6. Repeat steps 3-5 above for each contact type
7. 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.

Which columns are displayed and their names is customizable form from the Invoice Configuration section on the LogiSense Integration tab.

1. Navigate to the LogiSense Integration tab
2. Click on the Invoice Configuration button
3. Select which columns you would like to see in the Visualforce page by selecting the checkbox
   Image Added
4. Optional, rename the Label value
5. Click , Save

Any changes will take effect immediately across all account layouts that have are configured to show the Visualforce page.