Database Segmentation Fields


Now that you've stepped through How to create Database Segments, you might be wondering, how do I know which field matches up with the information I want to display? This article will briefly go through where the data in Database Segments comes from for each field.

The information in Database Segments primarily comes from: 

  • Fact Finder
  • Superannuation
  • Assets/Liabilities
  • Insurance

If you have created a Custom Fact Find, then that information will also be a selection in "Fields to Display". If you've stepped through How to set up a Custom Fact Find, you will see that "Example Fact Find" section is displayed in the list below:

Default Fields

If you have not set up any custom fact finds, the default values in your "Fields to Display" are:

Fields to Display Data Source(s)
Account Codes
  • Fact Finder -> Basic Information -> Account Codes
  • Fact Finder -> Contact Details
All Addresses 
  • Fact Finder -> Contact Details
  • Assets/Liabilities -> Assets
  • Fact Finder -> Basic Information
  • Fact Finder -> Business Details
  • Fact Finder -> Consultants 
Contact Details
  • Fact Finder -> Contact Details
  • Fact Finder -> Contact Details
  • Fact Finder -> Dependants
  • ToolBar -> Diary Icon
  • Fact Finder
Estate Planning 
  • Fact Finder -> Estate Planning
Existing Insurance
  • Fact Finder -> Insurance
  • Fact Finder -> Expenses 
File Notes
  • File Notes -> File Notes
  • Assets/Liabilities
  • Fact Finder -> Superannuation
  • Fact Finder -> Insurance
  • Fact Finder -> FOFA Compliance
  • Fact Finder -> FOFA Compliance
FOFA Services
  • Fact Finder -> FOFA Compliance
  • Fact Finder -> Goals & Objectives
Health Details
  • Fact Finder -> Health Details 
  • Fact Finder -> Income 
  • Tools -> Cash Flow Defaults
  • Cash Flow -> Scenario Settings
  • Assets/Liabilities -> Liabilities
  • Fact Finder -> Basic Information -> First Name + Last Name
  • Fact Finder
  • Fact Finder -> Basic Information
  • Fact Finder -> Superannuation
  • Assets/Liabilities -> Assets
Recommended Insurance
  • Insurance -> Recommendations
Risk Profiles
  • Fact Finder -> Risk Profiles
  • Fact Finder -> Superannuation
  • Tasks -> Task Notes only
  • Fact Finder -> Entities

The Different 'Entity' fields

There are 4 different field sets that pull similar data:

  • Entity
  • ParentEntity
  • Client
  • Partner

Creating useful Database Segment reports will require a good understanding of the purpose of these field sets. Conversely, misusing these field sets can often cause your reports to be incomplete, if they work at all.


The Entity set of fields is the foundation of most Database Segment Reports. This can pull information from any type of entity - those being Client, Partner, Joint, Company, Superfund, and Trust. Appropriate filters should be used to help ensure a clean report result, as the Entity fields will try to create 1 row in the report for each entity type that matches the filters and has data for the fields selected. 


This fieldset will look only at the Client entity type. The Client is always the primary or 'parent' entity in AdviserLogic - the lynchpin upon which a given client record is built. The system understands all other entities by their relationship to the Parent Entity. 

This field set allows for easy high-level reporting, as it will attempt to force the report to show 1 row per client record (which could include data for all entity types within that client record). Do not try to use ParentEntity and Entity at the same time, as this will cause inaccurate results.

Client and Partner

These field sets have very specific focuses - each is a limited form of the 'Entity' field set, but with automatic filtering applied to focus them on Client entities or Partner entities, respectively.

Advanced Users of Database Segmentation will find more success by using the 'Entity' field set in combination with some filter settings. The Client and Partner field sets are good if you just need a very simple report - say, a list of names of Partners.

Important to note: do not use Client and Partner in the same report. They usually will prevent the report from working, but if it does produce data, that data cannot be relied upon.


Difference between the Address fields

AdviserLogic provides three different types of fields to retrieve data about the addresses of clients:

1. Address

This field provides information on the addresses of each client that have been filled out. E.g. In Fact Finder -> Contact details, if you have entered in both home and work address for a certain client, then using this field will return two addresses; home and work.

2. All Address

This field allows you to select specific aspects from any address of the client:

  • Home
  • Mailing
  • Work
  • Other

3. Default Address

The addresses displayed in this section are what you set in Fact Finder -> Contact Details -> Options -> Preferred Contact Address

If the Preferred Contact Address has been left as blank, then the address generated is the Mailing Address.

Commonly Used Fields


This section is equivalent to a client's profile. Any piece of information relating to a client will be an option in the Entity drop down list e.g. whether the client has insurance, the time that the last file note was created against the client, etc.

This section is commonly used to generate a list of clients for:

  • Review dates (Last Review Date, Review frequency, etc)
  • Type of insurance a client possesses (Life, Trauma, TPD, etc.)
  • Total assets/liabilities a client possess

Entities also include Partners, Business Clients, Superfunds, Companies, and Trusts


This section provides all the information a client has in relation to insurance e.g. insurance type, insurance sum, insurance description etc.

This section is commonly used to generate a list of insurance information for each client.


This section is all about information associated with superannuation funds. You can set more filters in "Define Filters" selection to specify a certain type of super and/or information associated with the super.

This section is commonly used to generate a list of all the SMSFs existing in the system or other types of funds. 

Have more questions? Submit a request