Considerations and Guidelines for Custom Report Types

When creating a custom report type, keep these considerations and guidelines in mind.

Considerations

If a report type’s primary object is a custom object and the custom object is deleted, the report type and reports created from it are deleted.
When you remove an object from a report type, all references to that object and its associated objects are removed from all reports and dashboards based on that report type.
If a parent record doesn’t have a related child record, the child object’s fields are blank in a report. For example, when you run a report on Accounts with or without Contacts, the Contact fields are blank for the accounts that don’t have contacts.
In a report where object A may or may not have object B, you can’t use the OR condition to filter across multiple objects. For example, you can’t apply Account Name starts with M OR Contact First Name starts with M.
If you add custom fields from different objects that have the same API name, only one of the fields displays when the report type metadata is deployed to another environment. For example, adding both Account.Custom_Field__c and Opportunity.Custom_Field__c results in one visible Custom_Field__c.

Users can view roll-up summary fields on reports that include data from fields that they don't have access to view. For example, users who don't have access to view the Price field on an opportunity product can view the Total Price field on opportunity reports if they have access to the Total Price field.
You can add up to four levels of a relationship via lookup. For example, for an account, you can have the account owner, the account owner’s manager, the manager’s role, and that role’s parent role.
Reduce the amount of time it takes to find fields in a report by grouping similar fields together in the custom report type layout. You can create page sections to group fields that are related to one another, and you can group fields to match specific detail pages and record types.

Did this article solve your issue?

Let us know so we can improve!