FastTrack bootcamp is also available for Operations
What is FastTrack?
FastTrack is offered to larger customer (250 seats plus) and the FastTrack team get involved to guide the customer and partner to make sure the project is successful.
This page is offers a good overview of FastTrack and what it’s all about
FastTrack for Dynamics 365 is our customer success service designed to help you move to Dynamics 365 smoothly and confidently, so you can realize business value faster. When you participate in the FastTrack program, you will receive guidance on best practices and how to plan for successful rollouts. You will also learn ways to enable new users and expand capabilities – all at your own pace. Additionally, you will have access to Microsoft engineering resources committed to make your experience with Dynamics 365 a success.
The FastTrack offers skype sessions, workshops and regular touch-points to make sure the customer is on track.
If you are eligible for the FastTrack program then Microsoft will be involved in your project and help ensure the successful implementation of Dynamics 365 by using their FastTrack process and experience implementing Microsoft Dynamics 365.
Microsoft’s FastTrack team isn’t one or two people but many different experts.
It’s a 4 day intensive course, which covers most aspects of a Dynamics project
Order of flows is used if multiple flows are available for your security roles
Users can switch Business process flows if their security roles can see multiple
A team must belong to a business unit
A team can own records
Business units have a default team created by Dynamics 365, you cannot edit these or add/remove users.
You can add a custom control to data types – data and time, multi-line, single line
There are 9 entities enabled for auto numbering – contracts, cases, articles, quotes, orders, invoices, campaigns, categories and knowledge articles
If you enable Yammer you cannot disable it
Different email architecture/Dynamics 365 mixes
Local exchange server – On premise Dynamics 365
Office 365 exchange – Dynamics 365 online
Office 365 exchange – Dynamics 365 on premise
Server side sync – Dynamics exchange integration allows appointments, tasks and contacts to be synchronized (optional)
Dynamics 365 for Outlook Client
Dynamics 365 App for Outlook
Entity properties which cannot be disabled once enabled
Business Process flows
Offline capability for Dynamics 365 for Outlook
Entity properties you can disabled once enabled
Enable for SLA
Allow quick create
Single record auditing
Multiple record auditing
Enable for phone express
Reading pane in Dynamics 365 for outlook
Use custom help
Folder tracking is tracking folders using server side sync and not limited to one email client
Folder tracking only works with server side sync
Folder tracking only works with exchange
Tracked folders work with Exchange Inbox rules
The tracking folders feature must also be enabled by your administrator
You can only track folders or subfolders inside your Exchange Inbox
You can set up multiple folders that link to the same regarding record
You can include an untracked folder inside a tracked folder
If you no longer need to track a folder, it’s a good idea to untrack it for performance reasons. To untrack a folder, remove it from the Folder-Level Tracking dialog box.
You can track emails only in folders under your Inbox folder in Exchange. Other folder emails cannot be tracked.
You can track up to a maximum of 25 folders per user account
Any manual changes done to the regarding object in the tracked activity records in Dynamics 365 will be overridden the next time server-side synchronization kicks in. For example, if you have set up a mapping between the Adventure Works folder and the Adventure Works account, all the emails in the Adventure Works Exchange folder will be tracked as activities in Dynamics 365 with the regarding set to the Adventure Works account record. If you change the regarding to some other record, it will automatically be overridden the next time server-side synchronization occurs. To change the regarding for any email, move the email to a different folder such as the Inbox.
App for outlook works at server level
Dynamics 365 for Outlook
Server side sync
Email router is dead soon
Server side sync doesn’t need a users outlook to be open
Server side sync works with Dynamics 365 online or on premise and Exchange online or Exchange on premise. Any mixture of those
Mailboxes are created for users and queues
Separate options for incoming and outgoing email
You can set either or both incoming and outgoing sync to none
Forward Mailbox – you can set multiple users to be configured with a forward mailbox
Stop users synchronising with system settings à Email à incoming email and outgoing email to none
Dashboards can be made available for tablets
In properties you can enable dashboard for tablets and individual sections for mobile
Only first 5 tabs or 75 fields/10 lists appear on mobile client
Set available on Phone checkbox to show/hide tabs in mobile
Collapsed tabs still count
Only 5 tabs will show even if it’s less than 75 fields
You have to put fields in the first five tabs for them to appear in a mobile client
Mobile can have specific mobile only controls (sliders)
Business rules can
Show Error Message
Set field values
Clear field values
Set default values
Set business requirement level
Set Visibility (Show or hide fields)
Enable or disable fields
Validate data and show error messages
Create business recommendations based on business intelligence.
Business rules can have 10 Conditional Branches
Business rule scope
All forms – all forms, quick create and main
Entity – can run form and server side.
Entity – server level will run on create or update
Entity – if server enable will run when data is imported
Single form scope – only runs for the specified form
To change scope of business rule you must deactivate first
Sub-grid for Access Teams (must enable entity for access teams)
Access team templates will applying a standard set of privileges (read, write, delete, append, append to) rather than having to set this up for each individual user/team.
Access Team templates are enabled on an entity basis and you have to enable Access Teams on the entity in the communications and collaboration
When records are deactivated, access team permissions are not effected
Access teams don’t have security roles
Access teams can’t own records
Access teams are created and managed by CRM
An access team is created when you have added the first user
Access teams are not visible in default team views
Sharing records via access teams isn’t displaying in the sharing screen
Access teams can’t be used in resource scheduling
Multiple access teams can be linked to a single record
Access Team Templates, support dynamic record sharing. With the members of an access team being given privileges on specific records based on the access team template.
access teams do not have roles and cannot own record
Facts and stats about Access Teams, the bits below are useful for those study MB2-703
You can add more than one Access Team template for each entity
The default number of access teams templates for each entity is two
The number of access team templates you can have for each entity is controlled by the MaxAutoCreatedAccessTeamsPerEntity deployment setting.
MaxEntitiesEnabledForAutoCreatedAccessTeams deployment setting has a default value of 5. This controls the number of entities it’s possible to enable for auto-created access teams.
You can change the MaxEntitiesEnabledForAutoCreatedAccessTeams , MaxAutoCreatedAccessTeamsPerEntity only on Premise installations and you cannot edit them for Online.
A system generated Access Team isn’t created for each record until you add a user to the sub grid on the entity.
if you delete the team, this is the same removing all the members in the sub grid on the record.
if you change the access rights on Team Template this will only change the access right to new entity records/access teams. Any records already created will use the previous set of privileges.
Access teams with Share access right ticked will mean any user who is in access team will be able to add (share) others to the access team for that record.
Users cannot grant privileges they do not have. So a user can only add new members to an access team where the access team template has create privilege only if that user has the create privilege for the entity.
Access Teams created automatically by adding users to them are not shown in the system team views
Access Teams created automatically can be seen by doing an advanced find and select Team Type = access
Access Team created automatically have the is system managed field set to true
Access Teams can be un ticked on an entity (unlike Queues)
If you want to delete a Access Team Template you will need to remove all the sub grids using that specific Access Team Template before you can delete it.
Below are the following entity assets
Relationships (1:N, N:1, N:N)
You don’t have select all the entity assets
You can add the entire entity by checking the Add All Assets Checkbox
You can manually select specific assets by selecting them
Fewer assets means fewer dependencies and quicker deployments
Business process flow
You must enable Business process flow on an entity
Once an entity is enabled BPF you cannot disable it.
Each entity can have no more than 10 activated business process flows
Multi-entity process can use no more than five entities.
A business flow has a primary entity but can span multiple
Branches can be only 5 levels deep
Set scope to Entity if you want a business rule to run on the server, not just on the client side
Business rules are not triggered when you save a record
Business rules are triggered when a record is opened or when a field is changed which the rule conditions are set to check e.g Form OnLoad and Field OnChange
Business rules action will run only if condition is true
Rollup fields recalculate once an hour
Rollup fields supported – Whole Number, Date and Time, decimal, currency
Maximum 100 per organisation
10 rollup fields per entity
If you make a rollup for a currency field, it will create one for the base
Rollup fields not supported – Option set and Lookup
Aggregate value of records related to a specific record
Rollups fields are asynchronous, they don’t run in real time
Rollup fields can be run by workflows or business rules
Rollup fields can be refreshed manually or triggered by a workflow
Rollup Fields are automatically rolled up 12 hours after they are created
A workflow can’t be triggered by the rollup field updates.
You might have missed or ignored Microsoft’s post on the new update cadence because few people use the term update cadence. What update cadence refers to is the NEW MICROSOFT DYNAMICS RELEASE schedule, the change is two major updates to Dynamics 365 online twice a year at the same time (in each region) with no way to opt out or schedule.
WHAT! You mean Microsoft Dynamics 365‘ in a region will upgrade at the same time potentially causing thousands of production instances to break and flood Microsoft support! If the next release has as many bugs as version 9 it will be interesting.
If your region is one of the later regions than it should contain fewer bugs, wooohoo.
Get up to speed
The video from Business Application summit goes through the changes and answers common questions
For customers who are running older versions of Dynamics 365, we will continue to provide you with the ability to schedule an update to the latest version and want to make sure this effort is as seamless as possible through continuous improvements in our update engine.
For Dynamics 365 (online) Customer Engagement applications, we sent update communications in May 2018 to all customers running v8.1 and have scheduled updates. Customers running v8.2 should plan to update to the latest version by January 31, 201
The release notes for the October 2018 update will be published on July 23, 2018.
Will I still be able to schedule the major updates?
Yes, we will provide an update window within which you can schedule a major update. If you don’t set a time within the window, Microsoft will schedule an automatic update for your organization and communicate the date.
The new release cadence will make sure no customer gets left behind (even if they want to) it forces updates in October and April. You won’t be able to opt out..
Why would you force everyone to get the new version of Microsoft Dynamics 365 at the same time? It’s much easier to find and fix bugs if everybody is on the same version, this should cut the number of calls Microsoft support gets for fixed bugs.
To help Microsoft will publish release notes months before the update happens and you can disable disruptive features.
How it works now
Microsoft Dynamics 365 has 2 major releases per year, you can opt to only one of these but you have cannot miss two. You can request when you want your Dynamics instance upgraded and then book your date.
We could only test production when Microsoft upgraded it, the sandpit environments should be the same, each Dynamics environment is different. Environment settings are different, you can’t copy the server settings and you can’t copy database indexes. For big Dynamics database it’s difficult to copy the data and you rarely want developers viewing production data. Microsoft work in a single instance level but with Dynamics 365 online you have a groups of instances.
How it will work
The two major releases are mandatory and not optional. You cannot opt out of accepting a major release, you can opt in to take earlier but on a date specified by Microsoft they will update Dynamics 365 online in a region.
Release notes are available before time
You can update sandbox instances before
Companies can test the functionality before on a sandbox and read the release notes to prepare. The downside is you can’t miss a release and you can’t schedule it to later, this means companies will need to test earlier and test quickly.
Why are they changing
Microsoft says the reasons for changing
Lower Supportability costs
Early visibility and access to updates
You can to opt-in to new features and have better performance and reliability e.g. they release the functionality but don’t force you to use it. Microsoft will keep API’s and features backwards compatibility.
It will be easier for Microsoft to support everyone if they are on the same version, more instances will test newer versions.
In my experience it wasn‘t new features that caused problems it was the bugs in existing functionality. Version 9 saw Microsoft add bugs into Solution importing, stage for upgrade, auditing, performance issues.
Microsoft moving to continuous deployments and SAFE deployments are a step in the right direction and bringing better practices. Early testing of updates with companies who have opted in for 1st deployments and Microsoft. With more deployments Microsoft should fail faster and fix problems quicker.
The Admin opt-in to try new features is interesting, it’s for major disruptive features!! the wording scares me.
Microsoft are supporting production Dynamics 365 implementations and customers business. In Version 9 there has been a significant increase in the number of bugs raised to Microsoft. I have never known so many projects to have problems with Microsoft Dynamics, in quantity and severity of bugs. Some bugs seem so obvious that no one could have tested the functionality. I assume these problems were due to infrastructure changes made by Microsoft.
How will developers need to change
Developers must read the release notes, all 200 plus pages of release notes to understand the changes. Microsoft proposed new features but then pulled them at the last-minute, will this happen?
Release notes are living documents, constantly being updated, so you might read the notes and then next time you read the notes they could have changed.
Microsoft mentions investment in automated testing such as Easy Repro. Capgemini Dynamics team have used Easy Repro on projects, read more in the posts below
They scheduled the version 9x release for July but ended up being released at end of November, how will this slippage and version content work now they are being transparent and showing what they will release and having a fixed date?
On the Q&A Microsoft want to know the challenges of upgrading everyone on a set a date with no way to delay it?
The time and cost of testing production and the risk of Microsoft breaking production systems by adding bugs. Microsoft asking this question makes me wonder if they understand the disruption releases cause and the speed support takes to resolve issues. In the Q&A it felt Microsoft thought unsupported customisations caused the problems but common problems on major upgrades is Microsoft breaking fundamental functionality.
Early release notes are living documents which could change and update. The previews are useful and continuous delivery should remove barriers to Microsoft finding and fixing bugs quickly (if they have the resources to do so).
The plan seems good, but it depends on Microsoft execution. It’s good Microsoft is getting users to sign up for early release and not using everyone to test their new functionality.
Microsoft says they won’t leave anyone in a broken a state, lets hope so.