Browse


Narrow Search

Feature
Role
Can't find what you need?
Contact Us

Reset Search
    Search Knowledge Base
 
Article

Creating Custom Report Types

« Go Back

Information

 
Summary
-
Previous: Build dashboards
  1. From Setup, click Create | Report Types.
  2. Click New Custom Report Type.
  3. Select the Primary Object for your custom report type.
  4. Enter the Report Type Label and the Report Type Name. The label can be up to 255 characters long. The name is used by the SOAP API.
  5. Enter a description for your custom report type, up to 1000 characters long.
  6. Select the category to store the custom report type in.
  7. Select a Deployment Status:
    • Choose In Development during design and testing, as well as editing. The report type and its reports are hidden from all users, except those with the "Manage Custom Report Types" permission. Only users with that permission can create and run reports using report types in development.
    • Choose Deployed when you're ready to let all users access the report type.
  8. Click Next.
  9. Click the box under the primary object.
  10. Select a child object. Only related objects are shown.
  11. For each child object, select one of the following criteria:
    • Each "A" record must have at least one related "B" record. Only parent records with child records are shown in the report.
    • "A" records may or may not have related "B" records. Parent records are shown, whether or not they have child records.
  12. When Users are the primary object, select child objects by field-for example, Accounts (Account Owner) or Accounts (Created By).
  13. Add up to three child objects. The number of children depends on the objects you choose.
  14. Click Save.
  • If you select that object A may or may not have object B, then all subsequent objects automatically include the may-or-may-not association on the custom report type. For example, if accounts are the primary object and contacts are the secondary object, and you choose that accounts may or may not have contacts, then any tertiary and quaternary objects included on the custom report type default to may-or-may-not associations.
  • Blank fields display on report results for object B when object A does not have object B. For example, if a user runs a report on accounts with or without contacts, then contact fields display as blank for accounts without contacts.
  • On reports where object A may or may not have object B, you can't use the OR condition to filter across multiple objects. For example, if you enter filter criteria Account Name starts with M OR Contact First Name starts with M, an error message displays informing you that your filter criteria is incorrect.
  • The Row Limit option on tabular reports shows only fields from the primary object on reports created from custom report types where object A may or may not have object B. For example, in an accounts with or without contacts report, only fields from accounts are shown. Fields from objects after a may-or-may-not association on custom report types aren't shown. For example, in an accounts with contacts with or without cases report, only fields from accounts and contacts are available to use. Also, existing reports may not run or disregard the Row Limit settings if they were created from custom report types where object associations changed from object A with object B to object A with or without object B.
 
Next: Building Reports with Cross Filters

Feedback

 

Was this article helpful?



   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255

 

Apto