TutorialKart.comHow to Add Entity Assets and Artifacts to a Dynamics 365 App
In our previous Dynamics 365 tutorial, we have learned how to create custom Dynamics 365 app using App Designer. In this tutorial, we will learn how to add entity assets and artifacts to a Dynamics 365 app.
In the classic Dynamics 365 App Designer, artifacts are the main app components such as sitemap, dashboards, business process flows, and entities. Entity assets are the parts of an entity that users work with inside the app, such as forms, views, charts, and dashboards. In newer Microsoft Power Apps documentation, entities are commonly referred to as tables, but many Dynamics 365 environments and older App Designer screens still use the term entity.
Entity Assets and Artifacts in Dynamics 365 App Designer
Before adding components, it is useful to separate the two terms used in App Designer.
| App Designer term | What it means in a Dynamics 365 app | Examples |
|---|---|---|
| Artifact | A top-level app component that shapes navigation or app behavior. | Sitemap, dashboard, business process flow, entity. |
| Entity asset | A component that belongs to a selected entity and controls how users view or edit records. | Forms, views, charts, dashboards. |
When you create a role-based app, add only the components that the intended users need. For example, a sales app may include Accounts, Contacts, Leads, Opportunities, sales dashboards, and the relevant business process flows. Adding too many unrelated components makes the sitemap harder to use and can expose unnecessary options to users, depending on their security roles.
Adding an Artifact to Dynamics 365 App
On the right side of the canvas we will find different artifacts like Sitemap, Business process flow, Dashboard and Entities. We can add an artifact to Dynamics 365 App in two ways: by using the Add button on the command bar and by using the tiles in the components tab.
The artifact you add should match the navigation and business process of the app. A dashboard gives users a starting point with charts and lists. A business process flow guides users through stages. An entity gives users access to record data, provided that the required forms and views are also available in the app.
Add Dashboards to a Dynamics 365 App
Follow the step given below to add Dashboard to an App. Navigate to Components tab under Artifacts and select Dashboards.
- When you add a dashboard or business process flow to an app, the entities they use are automatically added to the app.
After selecting the dashboard, review the entities used by that dashboard. If a dashboard contains charts, lists, or record data from a particular entity, that entity must be part of the app so that the dashboard can load correctly for users.
- Use the same process to add Business Process Flow and Entity.
- After adding Dashboards, BPF and Entity in App designer click on publish button.
If the dashboard you want doesn’t exist in the default solution, create a dashboard by clicking Create New on the Components tab on the right side.
Add Entities to a Dynamics 365 App
To add an entity in a model-driven Dynamics 365 app, open the app in App Designer, go to the Components tab, choose Entities, select the entity that should appear in the app, and then add the required forms, views, charts, and dashboards for that entity. In newer Power Apps screens, the same concept may appear as adding a table to a model-driven app.
When selecting entities, add the entity only if users need to open, create, edit, or report on records from that entity. For example, an app for customer service users may include Cases, Contacts, Accounts, Queues, and Knowledge Articles, while a sales-focused app may include Leads, Opportunities, Accounts, Contacts, Quotes, and Orders.
Add Entity Forms, Views, and Charts to a Dynamics 365 App
Now we have to add entity assets like entity forms, views and charts to our custom Dynamics 365 App. To add entity form to an App, Navigate to App Designer canvas, Components tabs | Entity Assets | Forms.
To run our custom Dynamics 365 app, each entity that you add must have at least one active form. If you’ve selected multiple forms, the first active form that appears in the default solution will be used when users run the app.
For each entity, review these assets before publishing the app.
- Forms: Add the main forms that users need to create, update, and review records.
- Views: Add the public views that should appear in the app, such as active records, open records, or role-specific views.
- Charts: Add charts only when users need visual summaries inside the selected entity.
- Dashboards: Add dashboards that help users monitor the records and activities relevant to the app.
Do not add every available form or view unless the app is intended for administrators. A focused selection makes the app easier to use and reduces confusion when users switch between views or forms.
- Click on Details to expand the tile and see a list of forms that have been added.
Validate Dependencies Before Publishing the Dynamics 365 App
Validation checks whether the app contains the required components and dependencies. It is better to validate before publishing so that missing forms, views, dashboards, or related entities can be fixed before users open the app.
- Now click on Validate button as shown below to check dependencies.
If validation shows an error or warning, open the affected component and add the missing dependency. A common example is adding a dashboard without including the entity used by a chart on that dashboard. Another common issue is adding an entity without selecting at least one active main form.
Publish and Test the Custom Dynamics 365 App
After validation is complete, publish the app. Publishing makes the app changes available to users who have access through security roles and app permissions. After publishing, open the app as a user with the intended role and test the sitemap, dashboards, entity forms, views, charts, and business process flows.
Dynamics 365 app adds a presentation layer on top of your default application to provide your end users with an enhanced simplified user experience as shown below.
Common Issues When Adding Entity Assets to Dynamics 365 App
| Issue | Likely reason | How to fix it |
|---|---|---|
| Entity does not appear in the app navigation. | The entity was added but not placed correctly in the sitemap, or the user does not have permission. | Review the sitemap and confirm the user security role has access to the entity. |
| Dashboard does not load expected data. | A required entity, chart, or view used by the dashboard is missing from the app. | Add the dependent entity assets and validate the app again. |
| Users cannot open records for an entity. | No active main form is available for the entity in the app. | Add at least one active main form under Entity Assets. |
| Users see too many forms or views. | Too many entity assets were selected for the role-based app. | Keep only the forms and views needed for that app audience. |
Editorial QA Checklist for Dynamics 365 Entity Assets Tutorial
- Confirm that the tutorial explains both artifacts and entity assets, because users search for both terms.
- Check that the steps cover dashboards, business process flows, entities, forms, views, charts, validation, and publishing.
- Use the term entity for classic Dynamics 365 App Designer screens and mention table where the modern model-driven app terminology is relevant.
- Make sure the screenshots still match the classic App Designer flow shown in the article.
- Verify that the app is tested with a non-admin security role after publishing.
FAQs on Adding Entity Assets and Artifacts to Dynamics 365 App
How do I add an entity in a Dynamics 365 model-driven app?
Open the app in App Designer, go to the Components tab, select Entities, choose the required entity, and add the entity assets such as forms, views, charts, and dashboards. In newer Power Apps terminology, the entity may be called a table.
What is the difference between an entity and an entity asset in Dynamics 365?
An entity stores a type of business record, such as Account, Contact, Lead, or Opportunity. Entity assets are the parts used to work with that entity inside the app, such as forms, views, charts, and dashboards.
Why does App Designer automatically add entities when I add a dashboard?
A dashboard may use charts, lists, or views from specific entities. App Designer adds the related entities as dependencies so that the dashboard can display its data correctly inside the app.
Does every Dynamics 365 entity in an app need a form?
Yes, each entity that users open in the app should have at least one active main form. Without a usable form, users may not be able to create, edit, or view records properly from that app.
Should I add all forms and views for an entity to the app?
No. Add only the forms and views that are useful for the role or business process supported by the app. This keeps the Dynamics 365 app simpler and easier for users to navigate.