Az első lépések
Első lépésként adja meg munkahelyi vagy iskolai fiókját.
You can create a custom entity to store data that is specific to your organization. You can then show that data by developing an app that refers to the entity.
There are two ways to create an entity:
In both cases, Microsoft PowerApps automatically stores and helps secure the data. After you create an entity, you can create or modify one or more of its fields, and build relationships between entities.
Note: Before you create an entity, see the list of standard entities. These entities cover typical scenarios, such as accounts and contacts. If one of these entities will meet your requirements out of the box or after only minor changes, you can save yourself some time by starting with that entity.
Your entity appears in the list of entities in your database. To show your entity at the top of the list, click or tap the Type column header. The entities will be sorted by type, and all custom entities will appear above all standard entities.
All entities have five system fields. These fields are read-only. Therefore, you can't change or delete these fields, and you don't assign values to them.
|Display name||System field name||Data type||Description|
|Id||System field name||Big Integer||The unique identifier for the record.|
|Created By||CreatedByUser||Text||The user who created a record.|
|Created Record Date||CreatedOnDateTime||DateTime||The date and time when a record was created.|
|Last modified By||LastModifiedByUser||Text||The user who most recently modified the record.|
|Modified Record Date||LastModifiedDateTime||DateTime||The date and time when a record was most recently modified.|
If you create an entity from scratch, it also contains a custom field that is named Title. This field is set as the record's Title field. The Title field value is the user-friendly identifier of a record whenever you use that record in an app. You can change which field is the Title field, but every entity must have a Title field.
With the Microsoft PowerApps common data model we collect and store custom entity and field names in our diagnostic systems. We use this knowledge to improve the common data model for our customers. The entity and field names that Creators create help us understand scenarios that are common across the Microsoft PowerApps community and ascertain gaps in the service’s standard entity coverage, such as schemas related to organizations. The data in the database tables associated with these entities is not accessed or used by Microsoft or replicated outside of the region in which the database is provisioned. Note, however, the custom entity and field names may be replicated across regions and are deleted in accordance with our data retention policies. Microsoft is committed to your privacy as described further in our Trust Center.