While working with Business Process Flow in Dynamics 365, one of my colleague faced issue with “Next Stage” button. On clicking “Next Stage” on first stage, user is navigated to second stage but the second stage is not marked as Active. User is required to set it as active manually by clicking “Set Active” button.
Upon checking found that it is a known issue in Dynamics 365. Background workflows related to the entity on which the BPF is configured are causing the issue.
The issue is expected to get resolved by July 2017. For now as a workaround, we are required to deactivate all the workflows related to the entity for which BPF is configured and activate them again. Second workaround is to convert the background workflows to real time workflows.
Details are available at below community link.
Prior to the release of Dynamics 365, we are helped a lot by XrmToolbox to edit the sitemap without the need of editing the sitemap XML manually. However, with the release of Dynamics 365, it seems the plugin for XrmToolbox doesn’t support the editing of Dynamics 365 sitemap (given now it is possible for a Dynamics 365 deployment to have multiple Apps and each App can have their own sitemap).
So, what should we do now? There are 2 options to configure the Sitemap in Dynamics 365.
Option #1: Creating a new App
With the ability to create App in Dynamics 365, we can create a sitemap that is associated to the App. Following the guide from Microsoft on how to configure/design the app: https://www.microsoft.com/en-us/dynamics/crm-customer-center/design-custom-business-apps-by-using-the-app-designer.aspx
Option #2: Editing the Default Sitemap
Editing default sitemap is similar to what we used to do with XrmToolbox. However, with the unavailability of XrmToolbox…
View original post 151 more words
Very happy new year to all of my blog readers. This is my first post of the year and it could not have started in a better way. I am delighted to announce the new “Multi-Select Picklist control” from XrmForYou.com tools library. Showing a picklist attribute as multi-select is a requirement we get every now […]
Enhanced Business Rules in Dynamics 365 (Dynamics CRM)
There have been many changes in Dynamics CRM with release of Dynamics 365.
Business rule is one among those having major changes in after first introduced in Dynamics CRM 2013.
Business rules got new GUI (graphical user interface) to make it easier to understand and create a new Business Rule:
A new action added in this update is “recommendation” i.e. we can add recommendation to any field so that system suggest you to fill/select something specific.
We have created a test Business rule on case entity:
Task: If origin of case is “phone call” make “contact” field business required otherwise make it non-business required:
Step 1: Set condition in properties window in left right side.
In our case it’s if on entity case, field “origin” have value “phone call” :
Step 2: Drag and drop desired component to right mark to perform that action if condition evaluates…
View original post 130 more words
After completing the FieldOne Certification, I tried to list done some important terms and features of FieldOne and how they relate to standard CRM service module entities. As built on top of Dynamics CRM, it uses all the powers of Dynamics CRM with an addition to FieldOne services like Schedule Board, Mobile app, resource pay and advance scheduling algorithm.
The list is more of a quick guide to understand or revise the terms. See FieldOne learning material and other blogs (listed below) for detailed information on each term. Feel free to add more information or correct me in comments section below.
- FieldOne user who manages work order creation and scheduling.
- Usually manages work orders using FieldOne web client from Dynamics CRM.
- Notifies and dispatches a field agent for a particular work order.
- Field Agent
- Field agents are users who visits customer location to provide services.
- Uses FieldOne mobile application to get notified about work order assignment, work on work order, change status of work order, driving direction, etc.
- FieldOne users who analysis data by making use of reports, dashboards, etc.
- All standard features of Dynamics CRM applicable to reports and dashboard like export to excel.
- Consist of description of the issue or work to be performed, customer information, check list of steps to be followed for completing the work order, location, etc.
- These are related to a service accounts and not billing account. A customer can have one billing address and multiple service accounts.
- A particular work order goes through various stages before it is closed. These stages are Create, Scheduled, Dispatched, Serviced, Review / Approval, Invoiced & Inventory adjusted.
- Work orders can be created manually into CRM or automatically from Case, Order or agreement.
- Power full tool that helps Dispatcher to schedule work orders and assign resources based on availability, territory, skill set, etc.
- Shows list of work orders as well as map.
- Allows rescheduling, updating status and reassigning of work order.
- Dispatcher can make use of various filters to find right resource to assign to a work order.
- Used to document skills
- These can be associated with resources and incidents.
- A resource can be selected for a particular work order based on skills possessed by the resource.
- Skills related to incidents can be helpful to find right resource who can fulfil incident needs.
- Accounts are customers.
- A customer can have one billing address and multiple service locations.
Based on above point, customers are divided in two types as:
- These are locations where service is to be provided.
- Service accounts can be used as billing address too.
- These are locations used for billing.
- E.g. Head office of a customer.
- Same functionality as CRM price list.
Security Roles & FLS
- Uses standard CRM security roles and Field security profiles.
Few OOB security roles specific to field one are (all prefixed with Field Service):
- Inventory Purchase
- Defines service areas.
- Zip codes are assigned to territories.
- Resources with similar zip code fall under relevant territory.
- Work orders are auto assigned to territories based on zip codes.
- These are users, crews, service center, etc.
- Resources can be configured to have work hours, time offs, etc. similar to user in CRM.
- Resources can be paid based on their time tracked for a particular work order and their status like Working hour, overtime, Travel, Break, Business closure, etc.
- These are products owned by customers and serviced by field agents.
- These are similar to contracts.
- Agreements can be used to auto create work order and invoices
- By using drag and drop of work orders from Work Order list or Map available on Schedule Board.
- Scheduling Assistant
- Auto Routing Scheduling
- Sky Mobile App
Microsoft Dynamics CRM 2016 Update 1 brings Email Signatures as an out of the box functionality. They can be used on Users or Queues (based on Teams).
Create a new email and you will see a new icon on the email designer to insert signatures:
To create more signatures, go to Personal Settings or, as an admin, Administration => Templates section.
Administration => Templates:
Notice Email Signatures is a new entity and it is part of the security roles. So, for instance, if the Customer Service Team requires to use Email Signatures, they should have access to the Email Signature Entity. See below an example security role:
Note: My current on-line build version is : 188.8.131.522 – DB 184.108.40.2069
You can find more information in the following Microsoft CRM article:
In normal business scenarios, a customer can be of type Account or Contact in Dynamics CRM. We also have fields of type Customer on some entities like incident which are lookup of type Account or Contact. But the creation of this type of lookup was not possible.
With CRM 2016 Update 1, customizer now has the ability to create Customer field for any OOB or custom entity.
With Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1, we now have an option to track feedback and ratings from customer for records in CRM with the click of a check box.
- A new option appears on general tab on an entity customization form called “Feedback” which once checked creates an 1:N relationship of that entity with feedback entity similar to activities.
- Users can use this entity to enter their response.
- Feedback entity itself is customizable.
You can enable feedback on entities to allow customers to write feedback or provide ratings for any entity record.
Scenario: Business wants to track feedback received from customers on the customer support experience. In this case you can enable feedback for the Case entity to receive feedback.
In case of multiple ratings against one particular record, with use of simple rollup field the ratings can be consolidated.