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?
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 the appropriate field types and name the query. Select Next and your data is now ready for unification.
Does this meet the goal?
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, remove rows that contain null values, and name the query. Select Next and your data is now ready for unification.
Does this meet the goal?
You use business process flows for all Dynamics 365 opportunities. Some opportunities are closed before business process flow durations are calculated. You need lo ensure that business process flow duration values are calculated.
Solution: When closing an opportunity, use the close as won dialog without completing the business process flow. Does this meet the goal?
You use business process flows for all Dynamics 365 opportunities.
Some opportunities are closed before business process flow durations are calculated.
You need to ensure that business process flow duration values are calculated.
Solution: Create a flow to update the Status Reason of the business process flow table record to "Finished" and the Status to "Inactive" when the opportunity is won.
Does the solution meet the goal?