Forum Replies Created
-
rinesh.r_93
Participant10 years, 6 months ago in reply to: Update Items MSCRM #5633We can use ListId as primary key from Quickbooks which we have to map with QuickbooksId in MSCRM.
rinesh.r_93
Participant10 years, 8 months ago in reply to: What if I make some fields removed or made invisible from the page where I want to put new fields. Will it cause any issues w #5626Please make sure if its not used for the integration. If it is filling with values after a sync, that means it is used in the mapping which will cause issues with the sync as it cannot find the field to fill the value.
So this will make the sync stop at the exact moment where it cannot find the field on the page.rinesh.r_93
Participant10 years, 8 months ago in reply to: It says “Error Occurred. Please Login again and Retry” when I try to click on the button, Update Opportunity To QBOE. I have #5625whenever we change DBSync Password, we have to update it on the User page details of Users who uses the button to sync details. Button works based on the details that we put on the User page.
If it is incorrect, it will throw the same error.rinesh.r_93
Participant10 years, 8 months ago in reply to: Are we able to send email to the accounts and/or contacts in MSCRM? #5624Absolutely! You are able to send email from several sources (i.e. from Outlook or via a web browser) to individual contacts, or even send to multiple contacts via a marketing campaign!
rinesh.r_93
Participant10 years, 8 months ago in reply to: If I have a Product in Salesforce as ” License:Test” and attaching it to an Opportunity, would I be able to sync the line it #5623No. It can only be referred by the Product which is specified on the left to the column operator(
.
Column stands for Parent child hierarchy in QuickBooks. If you use column operator(
between two products, it will be taken as a Parent child relation respectively.
In this case, License will be the Parent and test will be the child. Test can be referred by its Parent, License.rinesh.r_93
Participant10 years, 8 months ago in reply to: I am getting an Email Notification of an Error called Field Integrity Exception. Can somebody tell me what it means? #5622Field Integrity Exception comes when you have space between your transaction line items.
If you have a large number of records in QuickBooks, then it will throw this error while syncing and it can block the sync as it will identify the line space as a new item you have added which does not have a Name or Quantity. It will quit the sync and there is a chance of missing transaction on the other side if you did not check the records in Salesforce.rinesh.r_93
Participant10 years, 8 months ago in reply to: Issue in Linking QuickBooks to Salesforce. #5611Hello Anju,
Thank you for contacting DBSync.
Could you elaborate this issue in detail? So that we can analyse it get back to you.Thanks,
DBSyncrinesh.r_93
Participant10 years, 10 months ago in reply to: Could some one tell me about Record Types and Customer Service Entities? #5571As with any module within Microsoft Dynamics CRM, there are a key set of terms, phrases and elements that one needs to understand to effectively use it. Let’s take some time to review some of them. Customer records: Typical customer service requests using Microsoft Dynamics CRM will be managed in relation to an existing contact or account record. These contacts or accounts are within the same contact and account records which are used by other areas of business operations such as sales or marketing. A contact represents a person, just as it does in Microsoft Outlook. An account on the other hand represents companies, organizations or groups of people. While these are typical uses of accounts and contacts, different Microsoft CRM deployments might use these record types differently. Within the default application, they are collectively referred to as customers. When entering the customer value on a case, for example, the user might be able to choose either an account or a contact. Cases: Cases are the fundamental record type in service management and represent a single incident of service. Different organizations may refer to cases using different terms, including incident, ticket or service request. A customer can have many cases associated with a record at any point in time. Within Microsoft Dynamics CRM, users have the ability to see open and resolved cases from the customer record. Cases can also have knowledge base articles, subjects, products and entitlements associated with them, or as dependent record types. In addition to these entities, cases can have activities, which are another way of describing communications, that are associated with them so that everyone in the organization can see what’s happening with a particular case. The types of activities that are available by default include appointments, campaigned responses, emails, faxes, letters, phone calls, service activities and tasks. Activities can be associated with many different types of records within Microsoft Dynamics CRM. When looking at all the activities associated with an account or a contact, for example, the user can open the record and find the activities located under the closed or open activities list. Those activities that are considered to be closed are those that have been completed. Open activities are those that have either not been marked as completed or are pending completion on a different date and time. Resolution activities: After all activities regarding a case are resolved, the case itself can be resolved. Once the case is resolved, an activity type named resolution activity is created. This activity is found in the closed activities associated with a case. The resolution activity will display the case’s resolution as well as the amount of time spent on the case noted as billable time. Knowledge base articles: The knowledge base is a repository of informational articles used to assist customer service representatives in the resolution of a case. A knowledge base article is based on an article template that defines the sections found in the article as well as any formatting that might apply. In some organizations, the knowledge base is also used to provide Microsoft Dynamics CRM users with information about the company, product questions and answers, and any other kind of information that can be used to better equip employees to better handle customer inquiries, requests or issues. In addition to locating articles and associating them with cases, knowledge base articles can also be sent via email to a customer. These articles can be sent either via Microsoft Dynamics CRM’s interface or through Microsoft outlook. Entitlements: Entitlements are similar to contracts that are still available in Microsoft Dynamics CRM. However, entitlements, while they are similar to contracts in that they can be used to show the level and type of support a customer is entitled to, they do, however, allow greater flexibility which we will get into later. Entitlement channels: Entitlement channels can specify the type of service a customer is entitled to. There are five different entitlement channels: Phone, email, web, Facebook, and Twitter. Service level agreements, or SLA: Service level agreements are used to show a specific amount of time in which a customer is entitled to a response or particular products or services that they are entitled to as part of that service level agreement. Queues: A queue is a place to organize and store activities and cases that are waiting to be processed. Microsoft Dynamics CRM includes queues and work flow tools designed to improve how incoming comes for sales or customer service or other parts of the business are actually handled. A queue can be thought of as a box where items can go into or picked up by someone to handle. For example, an organization might have a support team who uses an email address of support at Contoso.com. If the support team gets an email sent to this address, an email of the team handles the support case from there and works to resolve the issue for the customer. Queues in Microsoft Dynamics CRM work the exact same way. While queues are commonly used along with a customer service module, other record types can be configured to use queues. The need to do this is defined by the organization and managed by a Microsoft Dynamics CRM administrator. The subject tree: The subject tree is a hierarchical list of subjects an organization can use to classify service cases and other records within the application. The subject tree is presented as a lookup field on the default case form and it’s often used to classify cases. By default, it can also be used to classify product records and knowledge base articles. Products: Products within Microsoft Dynamics CRM are found in the product catalog and can be related to a particular customer service case and can help to provide a more detailed view of cases, resolutions, and customer feedback at the product level. It is important to note that while products can be associated to a case to better categorize particular types of cases, there is no transactional aspect of cases that can leverage products for pricing or invoicing. In addition to the use of products along with cases, it is optional and might not be applicable to all organizations. Goals: In addition to reporting on and analyzing the information contained within Microsoft Dynamics CRM, organizations can use goal management features to establish and track progress against target values for key performance indicators. For service management, these might include metrics such as resolved or in process cases. The scheduling module: Microsoft Dynamics CRM includes a module for service scheduling. This module is technically part of the overall customer service module, but some organizations might not find it applicable to their business and will choose to not leverage that functionality. For those that do, there’s a wide array of features and functionalities that can be used. The scheduling module allows users to find qualified resources that are available to provide specific services to customers. For example, if a customer contacts a Microsoft Dynamics CRM user asking when they can have someone come to their location to provide a specific service, the user can create a service activity, and from there identify the service and the time frame they would like the service to be provided. The scheduling module has a built-in scheduling engine that will search all resources, including facilities and equipment, that are needed to provide the service and have availability to do so. Once the scheduling engine finds matches based upon those criteria, the Microsoft Dynamics CRM user selects those options and schedules the service. There are many types of organizations that can find use in this type of module, including professional services, healthcare providers, or types of organizations that schedule resources to provide services to their customer.
rinesh.r_93
Participant10 years, 11 months ago in reply to: Creating and Modifying Dashboards in MSCRM #5541A dashboard provides a way to present several areas of Microsoft Dynamics CRM data in a single display. This is useful for showing a quick overview of the status of a process, amount of activity going on or items which may need attention. Dashboards are often designed for a particular job role or a department and show information which would otherwise require the user to navigate through several screens to get the detail they need. Users can interact with the information and dashboards to explore and analyze it further to gain new insights and take actions on records to deal with any issue. As in charts there are system and personal dashboards. Personal dashboards can be shared, however, if it is composed of personal views, those views will need to be shared separately. Dashboards are made up of components, such as views, charts, iFrames or Web resources.
rinesh.r_93
Participant10 years, 11 months ago in reply to: Marketing Campaign Lifecycle – MSCRM #5540Microsoft Dynamics Marketing automated campaigns provide flexibility for rapid modification to enable real time personalized marketing. At the same time, an effective campaign involves planning. This is a typical campaign life cycle. It begins with planning. You want to determine the set of campaign activities, duration between each activity, and a lead scoring model. Then you move to building the campaign. You’ll build any activities or other entities required. Next, after building you’ll validate and check that all of the campaign activities are completed as required by Dynamics Marketing. After validating, you’ll activate the campaign. This means that you’ll turn the campaign on. Next, as the campaign runs, you’ll continue verifying the campaign that it’s running properly as well as monitoring. You’ll review the campaign results over the duration of the campaign and adjust accordingly, and you’ll also review reports.
rinesh.r_93
Participant10 years, 11 months ago in reply to: PDF document – MS CRM #5533MSCRM uses Microsoft reports for its reporting.
You can export such reports to pdf, it’s a bit of a nuisance for the user though, unless you do some work.
https://community.dynamics.com/crm/b/iotapcrminsights/archive/2015/05/04/downloading-or-emailing-microsoft-dynamics-crm-reports-as-pdf-word-or-excel-document-in-just-1-click
But the “standard” Microsoft reports approach would be the thing I would use by preference.
If those reports are not the right format for you then I would consider whether formatting a report to look exactly like the screen really adds much value.
You can spend a lot of time on formatting reports and users often don’t really care.
Sub grids are rather a complication because you (obviously) can’t click a button to open up a new tab on a report and you can only fit so much.
I would caution against trying to put too much in a single report.rinesh.r_93
Participant10 years, 11 months ago in reply to: Syncing custom MS CRM objects #5530We can integrate vendors from MSCRM to QuickBooks using DBSync as there is some customizations need to be done in your DBSync account.
rinesh.r_93
Participant10 years, 11 months ago in reply to: Security roles in MS CRM #5525Security roles are used to control access to records and features of Microsoft Dynamics CRM 2015. Rather than managing a user’s access individually, you will create a security role which describes the sort of access they will have based on their job function. Security roles describe various actions that a user can perform on records for each entity in the system and the access level they have to perform these actions on records, dependent on where the records are in relation to the users themselves.
For example:
Create a copy of the Customer Service Representative security Roles.
1. Click Microsoft Dynamics CRM.
2. Click SETTINGS.
3. In the Nav bar, hover over SETTINGS.
4. Click the right arrow.
5. Click SECURITY.
6. Click Security Roles.
7. Select the Customer Service Representative role.
8. On the Menu bar at the top of the list of Security Roles, click More Actions.
9. Click Copy Role….
10. In the Copy Security Role dialog box, in the New Role Name field, type “Customer Service Representative2”.
11. Clear the Open the new security role when copying is complete check box.
12. Click the OK button.