Dynamics 365 Flashcards
Entity
An item with properties that you track, such as a contact or account.
For an entity you might track properties such as company name, location, products, email, and phone.
Field
A property of an entity, such as company name.
Form
A set of data-entry fields for a given entity that matches the items that your organization tracks for the entity, for example, a set of data-entry fields that track a customer’s previous orders along with specific requested reorder dates.
Business process flow
An online process that walks users through a standard business process.
Standardize your business processes with the same stages and steps for each type of customer interaction. Business processes help everyone follow best practices.
Dashboard
Provides an overview of actionable business data.
Create a dashboard that provides lists and charts that shows a team’s performance at a glance.
Interface
The buttons, labels, and controls of the user interface.
If the users in your organization find the term Commit more familiar than the term Go, for example, you can change all the Go buttons to be Commit buttons.
Workflow
A set of rules that run on demand or are triggered to run automatically.
For example, a custom workflow could automatically send an email notification to an account owner when a specific condition or combination of conditions is reached.
When do you need to publish changes?
It’s basically like a commit. It saves work and customizations.
Publishing provides a way for you to save your work before you have finished and then come back and finish at a later time. Publishing is only required when you change a solution component. When you create or delete a solution component, publishing occurs automatically. Before you export a solution, you’ll be prompted to publish customizations. This is because any unpublished customizations won’t be included in the solution.
The following solution components require publishing when they are updated:
Application Ribbon
Entity
Entity Relationship
Field
Form
Message
Option Set
Site Map
Web Resource
What kind of user account should you use to test customizations?
You should always test any customizations you make with a user account that doesn’t have customization privileges. This way you can make sure that people without the System Administrator or System Customizer security roles will be able to use your customizations.
What is customization in Dynamics?
When you customize Dynamics 365 using the customization tools in the application, you’re adding or updating the metadata or data used by features that depend on the metadata. Because we know the kinds of data used to customize the system, we can take this data into account and add new features to Dynamics 365 without breaking your system.
What is metadata and why is it useful?
Today, modern business applications use a metadata-driven architecture so that people can customize the application without writing code. Metadata means “data about data” and it defines the structure of the data stored in the system. With this metadata, an application knows about any changes to the data structure and this enables the application to adapt as the data structure changes. Since the metadata is known, additional capabilities can be included that are tied to the metadata.
Why is using Javascript to manipulate the DOM unsupported?
Because Dynamics 365 is a web application these techniques work, but they are likely to break during an update because the names of the elements they reference are subject to change at any time.
Any JavaScript libraries used anywhere in the application must only interact with the documented APIs
What is a Dynamics Solution?
A Dynamics 365 solution is a file that you can import to apply a set of customizations.
Solutions exist so that a set of customizations can be purchased, shared or otherwise transported from one organization to another.
You can get solutions from AppSource or from an independent software vendor (ISV).
If you are just interested in customizing your organization, here is what you need to know about solutions:
Is creating a solution necessary?
When you customize Dynamics 365 directly, what solution do you work with?
How can you backup the customizations made in an organization?
Creating solutions is optional. You can customize your Dynamics 365 system directly without ever creating a solution.
When you customize the Dynamics 365 system directly, you work with a special solution called the Default Solution. This solution contains all the components in your system.
You can export your Default Solution to create a backup of the customizations you have defined in your organization. This is good to have in a worst case scenario.
What is a solution component?
What are some examples?
A solution component represents something that you can potentially customize and include in a solution.
Application Ribbon Business Rule Chart Entity Entity Relationship Form Security Role Web Resource Etc.
What is the purpose of having solution components when it comes to dependencies?
Most solution components are nested within other solution components. For example, an entity contains forms, views, charts, fields, entity relationships, messages, and business rules. Each of those solution components requires an entity to exist. A field can’t exist outside of an entity. We say that the field is dependent on the entity. There are actually twice as many types of solution components as shown in the preceding list, but most of them are not visible in the application.
The purpose of having solution components is to keep track of any limitations on what can be customized using Managed properties and all the Solution dependencies so that it can be exported, imported, and (in managed solutions) deleted without leaving anything behind.
What is a managed solution?
What is an unmanaged solution?
A managed solution can be uninstalled after it is imported. All the components of that solution are removed by uninstalling the solution.
When you import an unmanaged solution, you add all the components of that solution into your default solution. You can’t remove the components by uninstalling the solution.
What happens if you import an unmanaged solution that contains components that you’ve already customized?
When you import an unmanaged solution that contains solution components that you have already customized, your customizations will be overwritten by the customizations in the unmanaged solution. You can’t undo this.
Why would you create an unmanaged solution?
What solution can you export as an unmanaged solution?
Even if you don’t plan on distributing your solution, you might want to create and use an unmanaged solution to have a separate view that only includes those parts of the application that you have customized. Whenever you customize something, just add it to the unmanaged solution that you created.
You can only export your Default Solution as an unmanaged solution.
Can you import a managed solution back into your organization?
If you create a managed solution, you can’t import it back into the same organization you used to create it. You can only import it into a different organization.
How are solution applied in Dynamics? Consider system, managed, and unmanaged solutions.
From bottom up:
System Solution –> Managed Solutions –> Unmanaged Solutions –> Application Behavior
This means that unmanaged solution customizations take precedence.
Define the following:
System Solution
Managed Solution
Unmanaged Solution
Application Behavior
The system solution is like a managed solution that every organization has. The system solution is the definition of all the out-of-the box components in the system.
Managed solutions can modify the system solution components and add new components. If multiple managed solutions are installed, the first one installed is below the managed solution installed later. This means that the second solution installed can customize the one installed before it.
Unmanaged customizations are any change you have made to your organization through an unmanaged solution. The system solution defines what you can or cannot customize by using Managed properties.
This is what you actually see in your organization. The default system solution plus any managed solutions, plus any unmanaged customizations you have applied.
What are managed properties?
What type of solution can set managed properties?
Some parts of Dynamics 365 can’t be customized. These items in the system solution have metadata that prevents you from customizing them. These are called managed properties.
The publisher of a managed solution can also set the managed properties to prevent you from customizing their solution in ways they don’t want you to.
