When building a Power Apps application, developers often create custom tables immediately. But before creating one, check whether Dataverse already provides a standard table for your requirement.

What Are Default Tables?

Dataverse comes with standard tables for common business requirements, such as:

  • Account – Companies or organizations

  • Contact – People

  • User – Application users

  • Team – Groups of users

  • Currency – Currency information

These tables already contain commonly required columns, relationships, and functionality.

A Simple Example

Suppose you are building a Customer Management App.

Instead of creating:

Customer
Customer Contact

you can use:

Account
   ↓
Contact

Account can represent the company, while Contact can represent the people associated with that company.

If you need additional information, you can often add custom columns to the standard table instead of creating another table.

When Should You Create a Custom Table?

Create a custom table when the requirement represents a business concept that doesn't fit an existing Dataverse table.

For example:

Training Program
Audit Record
Project Evaluation
Employee Certification

These may require their own custom tables.

Quick Decision

Before creating a custom table, ask:

"Does Dataverse already have a table for this?"

If yes → Use or extend the standard table.

If no → Create a custom table.

Conclusion

Don't create custom tables just because you can. Start by understanding the business requirement and checking the existing Dataverse tables.

Using the standard Dataverse data model where appropriate can help you build cleaner, simpler, and more maintainable Power Apps solutions.