Personalized Community is here!
Quickly customize your community to find the content you seek.
Microsoft Customer Co-creation
Help impact how the tools and services you rely on are developed. Microsoft Customer Co-creation connects you directly with our engineers so you can provide feedback before a single line of code is written. Interested? Learn more at Microsoft Customer Co-creation
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
This is a series of connected posts to introduce document generation features with Xpertdoc Smart Flows, explaining the important steps and issues faced during XperiDo to Smart Flows migration.
This post explains the main steps when moving to Smart Flows from XperiDo. Also, this discusses some practical issues, important information to understand during the migration.
Select a user and add the Xpertdoc related roles to the user
At least one Xpertdoc project needs to be there to host all the flows, templates, data sets, connectors etc…
Connecting Xpertdoc with Dynamic 365 CE instance.
Following step will create the Smart Flow configuration record in Dynamics 365 CE if the Xpertdoc solution is found.
This is the most important step in migration. XperiDo components have to be importable to the Smart Flows environment. Xpertdoc (support) can help to convert XperiDo projects to one importable file and zip it.
Once the zip file is received, it can be extracted and a .xpa file is included in the zip file.
When the XperiDo project file is imported to Xpertdoc, the wizard will opt the user to select Flows, Templates, Data Sets and the connectors to be imported.
If any Flow is selected, the wizard will automatically include all the templates, data sets and the connectors for the selected Flow.
The user will not see the automatically selected components below.
The logic in this import step:
Flows listed – a flow for each template you could actually generate a document on in XperiDo. Behind the scene it will also import the needed templates and data sets needed.
Templates listed – all templates where the system cannot generate a flow. Behind the scene it will also import the needed data sets needed.
Data set listed – all data sets not used by any template.
Assets are not migrated through the .xpa file.
Need to import assets manually.
Business Applications communities