Reports can show slow performance when an object has a large number of rows. Then create an extension package to add reports that would run on standard and FS objects. In the above example, we can create a base package with reports running only on standard objects. One way to solve this problem would be to create packages without license dependencies. If your package has reports running on the standard objects and FS objects, then your package installation will fail in a customer environment that does not have an FS package. If the managed package object has a report running on an object from the Salesforce Field Service (FS), then your managed package has an FS dependency. Make sure you understand and document license dependencies when designing data models. Also, keep in mind the number of objects that can be joined in a single report. When designing a data model, the Denormalization approach could be advantageous with tradeoffs such as data redundancy, but with benefits such as data storage cost or optimal queries because of simple queries and fewer joins. In contrast, the Denormalization of the data model combines data into objects that help to speed up the retrieval process.
Normalization of the data model splits data into multiple objects that help to reduce data redundancy. Lookup relationships, on the other hand, allow the use of platform sharing capabilities and also allow you to make the relationship required or optional. For instance, master-detail relationships offer benefits such as out-of-the-box roll-up summary fields but they also enforce tighter links between objects such as cascade deletes of child records or enforcing security on child records. Relationships Master-Detail v/s LookupĬonsider the requirements when choosing relationship types. Also, you would have to create custom report types for custom objects. Consider the tradeoffs such as built-in security, standard report types, or out-of-box features if decided to create custom objects. Salesforce provides a rich collection of standard report types that you can tailor to your unique requirements. Review available standard objects from Salesforce to document required fields, relationships, and license types. Objects Standard Objects v/s Custom Objectsĭesigning a data model should consider object types (standard, custom, or external) along with record types, organization-wide default settings for object visibility, owners of the records within each object, and estimated number of records per object that can exist at any given period. In this technical blog post, we’ll take a look at various options for reports and dashboards when designing a data model, considerations you should keep in mind, and best practices to ensure your success.
0 kommentar(er)
