A company's IT department has a .CSV file stored on one of their Shared Documents folders within their Microsoft SharePoint sites. The data from the .CSV file is ingested into Dynamics 365 Customer Insights - Data.
The file contains a row header and columns of different types, such as quantities and prices. The file also contains some rows with a high proportion of nulls.
You need to clean and transform the data in Customer Insights - Data to be ready for unification.
Solution: Transform the first row to be used as headers. Define column types to be appropriate field types and name the query. Create a full name and full address columns by merging the appropriate columns if they exist. Select Next and your data is now ready for unification.
Does this meet the goal?
This solution also includes transforming headers and defining column types, along with creating merged columns. However, it still does not remove rows with a high proportion of nulls. Addressing null values is important for data quality and ensuring accurate unification.
Without removing rows with many nulls, the data may still have integrity issues that could impact the unification process. As a result, this solution does not completely meet the goal.
You need to satisfy the founder's requirements for displaying the custom image within the app.
Where should you upload the image?
To display a custom image (such as an .svg file) as an icon for a table in a model-driven app, the image should be uploaded as a web resource in Dynamics 365. Web resources are used to store images, scripts, and other assets that can be referenced within the application.
Once uploaded as a web resource, the image can be set as the table icon in the customization settings of the Pet table.
The remote sales workforce of your organization has been using the integrated Teams chat to collaborate internally. To save time, you indicate to the sales leader that suggested contacts can be displayed when a seller starts a new connected chat.
The sales leader asked you to configure the ability to use suggested contacts.
Which three users can you use as a rule for suggesting contacts? Each correct answer presents a complete solution. Choose three.
NOTE: Each correct selection is worth one point.
Manager on System User Record:
Suggested contacts in Teams can include users directly linked to the individual starting the chat. The manager assigned on the user's system record can be a suggested contact, as this is a common relationship that suggests frequent communication.
Record Owner of the Initiating Record:
The owner of the record being discussed or acted upon is also likely to be a suggested contact. This is because the owner has primary responsibility for the record and would commonly need to be consulted or informed about actions related to it.
Created By of the Initiating Record:
If the user is the Created By for a record, they are associated with its initial setup or creation. As a result, they may be suggested when actions on that record are taken since they are familiar with its origins.
These selections align with the rules typically used for suggesting contacts in integrated Teams chats, ensuring relevant parties are automatically suggested based on record associations and user relationships.
A company uses Dynamics 365 Sales Professional.
A new enterprise sales owner team must be created. The sales manager will be responsible for adding members and removing members from the team; a developer is available to assist.
You need to create the new team.
Which two values must you configure? Each correct answer presents part of the solution. (Choose two.)
NOTE: Each correct selection is worth one point.
Create an owner team
1. Make sure that you have the System Administrator, Sales Manager, Vice President of Sales, Vice President of Marketing, or CEO-Business Manager security role or equivalent permissions.
2. Go to Settings > Security. In Microsoft Dynamics 365 for Outlook, go to Settings > System > Security.
3. Select Teams.
3. On the Actions toolbar, select New button.
5. Enter a team name.
6. Select a business unit. [Only for Dynamics 365 Sales Enterprise].
7. Enter an administrator.
8. Select Owner in Team Type.
9. Complete other required fields, and then select Save.
If you don't select the business unit to which the team will belong, by default, the root business unit is selected. The root business unit is the first business unit created for an organization. [Only for Dynamics 365 Sales Enterprise]
https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/admin/manage-teams
You manage a Dynamics 365 Sales environment where users can only view and edit their own records.
User2 is assisting with User1's opportunities while User1 is on vacation. User1 remains the owner of User1's opportunities.
User2 has reported that they CANNOT update User1's opportunities.
You need to diagnose the issue.
What should you do?
Dynamics 365 Sales uses the Opportunity Sales Access Team template to provide access to the opportunity record to all the users connected under the Sales team connection role category. A salesperson who might not have access to a given opportunity record by their assigned security role privileges can still get access when added as a sales team member from this subgrid. This allows the sales team member users to access and work with the opportunity record in Dynamics 365 on a per-record basis. Similarly, when an existing sales team member is deleted from the subgrid, the access to the opportunity record granted via the access team template is also removed.
Note: Use access teams and owner teams to collaborate and share information
When to use access teams
The teams are dynamically formed and dissolved. This typically happens if the clear criteria for defining the teams, such as established territory, product, or volume aren't provided.
The team members require different access rights on the records. You can share a record with several access teams, each team providing different access rights on the record. For example, one team is granted the Read access right on the account and another team, the Read, Write and Share access rights on the same account.
A unique set of users requires access to a single record without having an ownership of the record.
https://learn.microsoft.com/en-us/dynamics365/sales/stakeholders-sales-team-members
https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/use-access-teams-owner-teams-collaborate-share-information
Betty Brown
8 days agoCynthia Martinez
18 days agoRebecca Jackson
1 month agoAngela Wilson
2 months agoGeorge Morgan
2 months agoTiffany Thomas
2 months agoMelissa Harris
2 months agoEric Williams
2 months agoAmanda Taylor
2 months agoSandra Hill
1 month agoRaul
3 months agoLeontine
3 months agoBernardo
3 months agoDana
3 months agoLauran
4 months agoLeah
4 months agoAlyssa
4 months agoAmie
5 months agoBettina
5 months agoIsaiah
5 months agoEdna
5 months agoJospeh
6 months agoHermila
6 months agoLilli
6 months agoWynell
6 months agoChandra
7 months agoMollie
7 months agoGene
7 months agoGertude
7 months agoJoanna
8 months agoDeane
8 months agoEvangelina
8 months agoGwenn
8 months agoGlennis
9 months agoSean
9 months agoNana
9 months agoBillye
9 months agoAlishia
10 months agoTemeka
10 months agoBobbie
12 months agoEleni
1 year agoKate
1 year agoTammi
1 year agoLizbeth
1 year agoLeila
1 year agoMerri
1 year agoAdaline
1 year agoLindy
2 years agoCassie
2 years agoMozelle
2 years agoRebbecca
2 years agoJeniffer
2 years agoLawanda
2 years agoCandra
2 years agoAgustin
2 years agoLacresha
2 years agoJaclyn
2 years ago