I'm trying to set up our software development company on Dynamics CRM 2016. I've customized almost everything I need such as accounts, leads and processes. However, It still feels that the CRM is designed for company with tangible products and shipping, etc...
Is there a way to setup Dynamics CRM for professional service company rather than product company?
This is not correct.
You can perform many actions that a professional service provider business model contains. For example, you can create and/or schedule:
Phone calls
Tasks
Appointments
Emails
You can also use marketing module for your services. Campaigns and quick campaigns.
You can gather leads, work upon those unqualified leads and convert them to opportunities.
You can also record invoices for your services as your products.
And so on ...
And the best part is that Microsoft has provided so many customization and development options in Dynamics CRM that you can almost use the XRM platform to just manage any type of relationship management. So, you can customize or even add new entities and relationships to suite your particular business needs.
One thing to keep in mind: First, always try to map your business requirements on the existing CRM processes so that you can take advantage of the out-of-the-box provided processes and reporting.
Update
The deployment/set up procedure for Dynamics CRM is same for all business domain. However, you may customize and extend Dynamics CRM, put those extensions and customizations in one or more solutions and then import those solutions over the target instances.
Update
You may override product price on quote (for example) by double clicking the product grid record on the quote form. See below image:
Related
I realize that Omnichannel is currently only associated with the Customer Service module for 365. However we have had a request from a client to provide Omnichannel for a sales process on a web site which links into a sales CE 365 organization (so in other words an agent to guide the user through the sales process via a chat if need be).
Is it possible to add in the Omnichannel module for sales in any way and if not any sort of alternate solutions we could follow for this requirement?
No, Omnichannel is built on top of Customer Service so having this first-party app installed is a requirement detailed in the documentation. I recommend you to contact your MS Account Manager and discuss this topic with them as depending on your requirements you might also need Power BI/Customer Voice/Power Virtual Agent licenses as well so maybe it's worth to explore some cross-application licensing.
There're alternative solutions in AppSource like CafeX LiveAssist and a few others, please make sure you filter by application to make sure they will work with Sales.
In PowerApps entity list page, we have default five fields Entity, Name, Type, Customizable & Tags
What does the Type field mean, I couldn't find any article related to this! Even Microsoft docs is a no go!!
I do know that Custom is the Type assigned to the tables created by us, whereas the default tables are grouped into two - Managed & Standard (refer screenshot).
But under what criteria do they get separated into the two groups?
This Standard type is part of Common Data Model (CDM) and PowerApps nomenclature:
CDM provides standard entities common across most industry domains – Sales, Purchase, Customer Service, Productivity among others. Leveraging the years of experience with Dynamics business applications and Office 365 and working with thousands of enterprise customers we have defined and implemented these standard entities that will connect to Microsoft’s first party business applications and support a broad ecosystem of ISV and customer solution development.
Learn more about CDM.
Managed is something like First party integration apps like LinkedIn, AI, Teams, etc. You will see publish prefix like msdyn_, li_, etc to see some identities. (maybe some third party Managed entities will follow this route, I'm not sure though).
I see some ADX portal like legacy entities marked as Standard rather than Managed, and some vice versa. I would say some sausage is being made, too early to look into that & that why documentation is missing.
Need help with deleting a user out of 15 different instances of MS CRM Dynamics. Is there a faster way of doing this rather than deleting the person out one instance at a time?
Whether it is crm onpremise or online, deleting systemuser is not possible (atleast by supported way) & not recommended to do in unsupported way (like SQL Delete in onpremise).
You can remove all the security roles & teams she/he is part of (take care of all WF, records they own)
Only you can disable by doing so in onpremise or by revoking license in O365 portal to replicate in crmol
If the AD account is removed/disabled it should replicate in Dynamics
No way to do in bulk across organizations anyway
Edit:
Based on comments, C# Console application can be developed, to iterate through multiple CRM connection strings & issue a sdk Service call to target system user record in each instance.
I'm registering a new 2013 on-line and I notice that there are two license types:
1. Microsoft Dynamics CRM Online
2. Microsoft Dynamics CRM Online Professional
What's the difference between them (in short)? I've read the description and I get the impression like "this one is yellow and the other is a car", so I simply can't compare.
According to this article, there are three (not two) different models and only one allows customizing the system (so it's only that one that there's any point showing to the customers).
What's up with that?!
In short, the headlines are:
All three licences allow access to CRM from all available clients eg browser, outlook, tablet, phone. (This is a big difference from the 2011 ESS CAL).
All three licences allow read access to all data, including custom entities. (subject to Security Roles of course).
Essential allows read/write access to activities, activity feeds and custom entities.
Basic allows everything in Essential, plus read/write to Accounts, Contacts, Cases, Leads. Also access to reports, and to create personal charts and dashboards.
Pro allows everything. Most notably Sales and Marketing (Opportunity, Quote etc, Campaign, Marketing List), plus service management (facility/equipment and all that).
Pro is needed to build customisations, but not to use them, which is where I think some confusion has arisen.
If you are talking about user licences there appears to be three distinct types.
It was a bit confusing however my general belief is:
1) Professional
This would be the Administration users who need to customize the system, build processes, templates, administer CRM, and run marketing campaigns.
2) Basic
Would be suitable for general users (ie:- ones that just need to work with entities but don't need to do much else). They can't do marketing campaigns which might restrict people who are given this licence. However your day to day staff should be fine with this as they have general access to entities as well as Reports and Dashboards etc.
3) Essential
Has very little access to core entities (even Account and Contact) so unless you have a client who wants to work with only custom entities then this seems like a pointless licence.
I've been told a few times that Business Units in CRM 2011 are "tricky" and shouldn't be set up lightly since they have irreversible consequences for a CRM 2011 implementation.
On the other hand, teams in CRM 2011 seem much more flexible in managing record security.
For what reason would I still choose to set up Business Units in CRM 2011? What can I do with Business Units that I can't with Teams (and vice versa)?
Business Units are important for the security concept of Dynamics CRM. They define a kind of a boundary within you can define specific roles or permissions. They are also used to represent an organization structure.
Teams are used for ownership of a record (new feature in CRM 2011), which is handy if you can't define a single owner. They are also used for easier sharing - you could share a record with a team, instead of sharing it with multiple persons. Another usage is to grant permissions to multiple users with grouping them into a team and assign a security role to the team.
Create a separate, new Business Unit (BU) at a higher BU level than all of the other User BUs (to avoid security role Parent:Child Business Unit permissions), then create a Team in that Business Unit.
Next, assign a security role to the new Team. Set the security role to be
restricted Read at the BU level (half a pie). Then, assign the "special" records to the Team.
Next, put the people who you want to see the records into the Team.
They will inherit the Team's security role permissions and will be the only ones in the company that can see those specific records.
You don't necessarily have to assign records to the team if you can just assign them to a user in that BU. However, you may need to assign the records to the Team if you don't have a user in the BU.
**NOTE: Watch out for Parent: Child Business Unit or Organization level permissions. The BU hiearchy would then play a role here.
*Be sure to test this before you put this into production**
Please follow below links which help alot
http://andrewbschultz.com/2011/08/09/business-units-bus-and-security-roles-in-microsoft-dynamics-crm-2011-solution-exports/
http://andrewbschultz.com/2011/06/17/the-architecture-of-team-security-in-crm-2011/
Thanks,