Hi everyone, There seems to be an issue with the BULK EMAIL settings within a contact. When I send out bulk emails from the marketing app, it also sends those emails to the contacts where the BULK EMAIL option is set to 'DO NOT ALLOW'. It does not do anything. Who can help and/or has the same problem? Thank you
↧
Forum Post: Setting Bulk Email does not work
↧
Blog Post: Microsoft Dynamics CRM Online 2016 Update 1 New Features- CRM App for Outlook
www.youtube.com/watch This training will cover the new features in Microsoft Dynamics CRM Online 2016 Update 1 / CRM 2016 Service Pack 1 for the CRM App for Outlook. This training will cover the following: Requirements New Features Demo Configuration/Deployment Components Architecture Troubleshooting Known Issues Additional Documentation https://community.dynamics.com/crm
↧
↧
Blog Post: Microsoft Dynamics CRM Online 2016 Update 1 New Features- Power BI
www.youtube.com/watch This training will cover the Power BI side with an overview and demonstration of capabilities. This training will also cover the CRM side and new features of Power BI in CRM. Topics include in the course include: Power BI introduction and overview Demonstration Requirements New Features Provisioning User Dashboard Components Architecture Troubleshooting & Known issues Tools and Resources https://community.dynamics.com/crm
↧
Forum Post: RE: organization not reachable after updated to 0.10 Dynamics 365 9.0
im currently investigating if it can be fixed by installing: www.nuget.org/.../Microsoft.IdentityModel.Clients.ActiveDirectory as the error references to assembly Microsoft.IdentityModel.Clients.ActiveDirectory or its dependencies. and you may also need to install .Net Core 3.0 SDK, Runtime and the client. keep you updated :)
↧
Forum Post: Upgrading CRM Dynamics from 8.2 to version 9.0 onPrem - Sharepoint Build Version is 16.0
Hi. We're planning to upgrade our onPrem CRM Dynamics from version 8.2 to version 9.0. The CRM Dynamics 8.2 is located on a Windows server 2012 R2. It has following external connections to other environments: - Microsoft SQL Server 2014 (external server running windows server 2012 R2) - Sharepoint version "16.0.4483.1000" (external server running windows server 2012 R2) Questions: 1. Can we upgrade CRM Dynamics to v9.0 without upgrading the other platforms? Or will we with CRM Dynamics 9.0 get problems using older Sharepoint server and SQL server? 2. Should we upgrade the server to Windows server 2016 or newer? Or is there no point for this? Guidance and general help is very welcome
↧
↧
Blog Post: Improve Dynamics 365 CRM Online or On-Premise User Adoption with additional 2 New Features!
User Adoption Monitor by Inogic the Microsoft Preferred App on AppSource has become an integral part of many organizations globally by helping them to review and administer Dynamics 365 CRM user adoption successfully. To make it more formidable and interesting we recently introduced two new features to it. So, let’s have a look at the following two new interesting features of User Adoption Monitor . Log-in & Log-out Check-in & Check-out Log-in & Log-out Until recently, it was only possible to track system login of users. But with this feature you can keep a track of log-in and log-out details of every user on a daily basis. Once the Log-in/Log-out entity configuration is completed, ‘Log-in’ button will appear on the ribbon of home grid. The user has to click on it before starting any activities in Dynamics 365 CRM. Once the user clicks on ‘Log-in’ it automatically changes and ‘Log-out’ button will appear on the home grid. After the activities are completed, the user has to click on ‘Log-out’ button before exiting from Dynamics 365 CRM. In this way you can easily track the amount of time spent by each user in Dynamics CRM system. Check-in & Check-out This new feature helps you to keep track of records that each user worked on. Once Check-in & Check-out configuration for a particular entity is completed, ‘Check-in’ button will appear on the ribbon of every record in that particular entity. The user has to click on it before resuming any task related to that particular record. Once the user clicks on ‘Check-in’ it automatically changes and ‘Check-out’ button will appear in its place. After the task is completed the user has to click on ‘Check-out’ button before leaving that record. In this way you can easily track the amount of time spent by each user on a particular Entity record. Thus, these features further enhance the capability of management to track and monitor Dynamics 365 CRM usage thereby giving them useful insight into the work carried out by their team. This will further help to organize training sessions for the team as per their individual requirement. To know more, download and explore the latest User Adoption Monitor solution from our Website . For a live demo or any of your unique requirements in User Adoption drop an email at crm@inogic.com
↧
Forum Post: RE: Record URL(Dynamic) creates wrong url of the task
Thanks, but for some reasons I can not find the mentioned columns in the SQL database. Also when I try to run a query to read the value of them, It can't find the columns.
↧
Forum Post: RE: dynamics 365 deployment manager error
Hello , Prior to that , check below points SQL server / service is up and running . alos check all the MS Dynamics services is up and running . check with differnet Deployment Administrator.
↧
Forum Post: RE: Newly created field is locked on the form
Hi James, Is the Field Requirement of this field system required? If so, you can not remove it from the form, you have to set it to optional.
↧
↧
Forum Post: RE: Record URL(Dynamic) creates wrong url of the task
Hi David, "ColumnName" is the field name, and you will look for the values i mentioned above in it. Please run this SQL statement to see the values; SELECT [Id] ,[ColumnName] ,[NVarCharColumn] FROM [MSCRM_CONFIG].[dbo].[DeploymentProperties] WHERE ColumnName in ( 'ADDeploymentSdkRootDomain' , 'ADDiscoveryRootDomain' , 'ADSdkRootDomain' , 'ADWebApplicationRootDomain' )
↧
Forum Post: Excessive Connections to SQL Server
Using Dynamics CRM 365 V8.2 On Premise We have noticed some strange behaviour when it comes to connections to the SQL Server made be our CRM Service Accounts. This is affecting some but not all of our customers as well as ourselves. We understand that the Async Service is multi-threaded and will make multiple connections to our CRM database on the SQL Server, but what we don't understand is why we have well over 200 connections (for an 8 user CRM system) that don't even have a connection to the CRM database, but to the MASTER database instead. What are these connections and what impact on resources does this have with so many connections option. This has got to have an impact on resources does it not. Has anybody else seen this behaviour before, and what's the best method to clean this up and stop it from re-occurring? Many thanks
↧
Forum Post: RE: Mobile application language
An update to this information, Hebrew is not a supported language yet, as mentioned by our documentation docs.microsoft.com/.../set-up-dynamics-365-for-phones-and-dynamics-365-for-tablets We are currently working with the Apple store page, in order to correct this error on their documentation.
↧
Blog Post: Dynamics 365CE (Common Data Service) vs. DevOps – problem brakujących zależności
Procesy DevOps / Continuous Integration na projektach Dynamics 365 (Common Data Service) powoli przestają być czymś niezwykłym. Sytuacje, w których dostosowania systemu, biblioteki .NET oraz wszelkie komponenty zależne są budowane, testowane oraz przenoszone między środowiskami ręcznie, powoli odchodzą do przeszłości. Dzięki udostępnieniu przez Microsoft narzędzia SolutionPackager – przechowywanie „rozpakowanych” dostosowań Dynamics 365 w repozytorium kodu staje się również powoli regułą. Podejście to umożliwia wersjonowanie, śledzenie zmian oraz scalanie plików dostosowań z wielu wykorzystywanych równolegle środowisk. I właśnie na tym ostatnim temacie, a konkretnie na pewnym problemie z nim związanym, chciałbym skoncentrować się w poniższym tekście. Wyobraźmy sobie sytuację, w której musimy utrzymywać 2 działające równolegle środowiska developerskie Dynamics 365. Pierwsze z nich może być odzwierciedleniem aktualnego środowiska produkcyjnego i być wykorzystywane w procesie naprawiania błędów. Drugie środowisko może służyć nam do tworzenia nowych funkcjonalności, które nie powinny być przenoszone na „produkcje” w ramach okresowych aktualizacji. Na początku oba środowiska posiadają zainstalowany identyczny zestaw dostosowań. W miarę upływu czasu i kolejnych, wykonywanych na nich prac, zaczynają się one jednak znacząco od siebie różnić. W końcu, w określonym momencie musimy dokonać scalenia dostosowań z obu źródeł. Teoretycznie, ponieważ posiadamy wszystkie pliki w rozpakowanej formie w repozytorium kodu, nie powinno być to trudne. Teoretycznie… Pierwszą dyskusyjną kwestią, o której warto wspomnieć, jest format „rozpakowanych” dostosowań Dynamics 365. Są to, jak powszechnie wiadomo, pliki XML. Każdy, kto kiedykolwiek pracował z tym formatem, zdaje sobie sprawę, na jakie trudności można natrafić w czasie scalania kilku wersji pojedynczego pliku. Oczywiście nie jest to problem nie do przejścia. Musimy liczyć się jednak z faktem, że przy bardziej skomplikowanych projektach, spędzimy sporą ilość czasu z wybranym narzędziem umożliwiającym porównywania oraz ręczne rozwiązywanie konfliktów i scalanie wspomnianych plików. Drugim, w moim przekonaniu znacznie poważniejszym problemem, który pojawił się w czasie integracji dostosowań z 2 działających niezależnie organizacji Dynamics 365, jest generowane w czasie eksportu drzewo brakujących zależności naszego rozwiązania. Czym jest omawiana struktura danych? Otóż zawiera ona listę komponentów, które nie są częścią eksportowanego rozwiązania, natomiast są wymagane do jego instalacji na środowisku docelowym. Każdemu brakującemu komponentowi zostaje nadany klucz, który (o zgrozo) może się różnić w przypadku 2 organizacji. Przykładowo – jeżeli do instalacji rozwiązania wymagana jest encja X, która nie jest jego częścią, w przypadku eksportu tego rozwiązania ze środowiska A może mieć ona Key=1, a w przypadku środowiska B – Key=666 (lub dowolną inną). Ponieważ dodatkowo lista zależności jest strukturą danych typu „drzewo”, brakujące zależności są od siebie wzajemnie zależne (relacja „rodzic-dziecko”), a dwa różne brakujące komponenty mogą posiadać w pliku eksportu identyczne (!) identyfikatory, automatyczne scalenie tej listy (dla przypomnienia – zapisanej w formacie XML) staje się praktycznie niewykonalne, a ręczne, w przypadku bardziej skomplikowanych solucji, urasta do rangi wielogodzinnego zadania. Oczywiście, możliwa jest implementacja narzędzia, które wczyta listy z wielu źródeł do pamięci, „przemieli” dostępne informacje, a następnie zapisze je w pliku wynikowym, który będziemy mogli zapisać w repozytorium. Co, jeżeli jednak nie dysponujemy taką aplikacją, a czas nas nagli, ponieważ potrzebujemy scalonego rozwiązania „na wczoraj”? Otóż możemy… usunąć zupełnie omawianą listę brakujących, zależnych komponentów z pliku solucji. Konkretnie, z obu wersji pliku Solution.xml, który pochodzi z 2 gałęzi w repozytorium kodu. Następnie dokonujemy scalenia wspomnianych wersji, pozbawionych kłopotliwych danych. Scalony plik wykorzystujemy do ponownego „spakowania” rozwiązania Dynamics 365CE (Common Data Service) do formatu ZIP. Jaki będzie efekt powyższej operacji? Lista brakujących zależności wykorzystywana jest przez mechanizm importu rozwiązania do walidacji poprawności importowanej struktury obiektów oraz rozszerzeń systemu. Walidacja następuje przed rozpoczęciem procesu importu. W przypadku ręcznego importu rozwiązania na środowisko, na którym przykładowo brakuje wymaganej encji A (która to widnieje na liście brakujących komponentów w pliku importowanego rozwiązania) – wynik importu będzie następujący: Co w przypadku, w którym usuniemy encję A z listy wymaganych, brakujących komponentów? W tej sytuacji system pozwoli na rozpoczęcie procesu importu rozwiązania. Proces ten jednak zakończy się niepowodzeniem. Błąd zwracany przez system jest następujący: „ Could not find PrimaryField for entity new_a”. Widzimy więc, że w obu przypadkach nie będziemy w stanie zaimportować do systemu naszego rozwiązania. W pierwszym przypadku – system powiadomi nas o nieprawidłowościach już na etapie walidacji poprawności rozwiązania, przed rozpoczęciem faktycznego procesu jego importu. W przypadku braku informacji o wymaganych komponentach proces importu rozpocznie się, jednak nie będzie zakończony sukcesem. Niestety, jak widać na powyższym przykładzie, informacja o błędzie nie w pełni oddaje charakter problemu, który wystąpił. Obawiam się, że w przypadku bardziej skomplikowanych zależności, komunikaty błędu mogą być mocno mylące, a przez to szukanie faktycznej przyczyny problemu może być mocno czasochłonne. Podsumowując – aktualnie nie mamy dostępnego żadnego gotowego rozwiązania, a także obejścia, gwarantującego nam stuprocentowy sukces operacji importu scalanego rozwiązania. Problem jest ewidentnie związany ze sposobem, w jaki Dynamics 365 (Common Data Service) generują listę brakujących zależności dla eksportowanej solucji. Czemu nie zdecydowano się na użycie, chociażby dostępnych, niezależnych od środowiska unikalnych identyfikatorów (GUID)? Tego niestety nie wiem. Microsofcie! Napraw to proszę! Tweetnij
↧
↧
Forum Post: Can't edit Web Query in Excel Dynamic Worksheet
Hi, We're having an issue when trying to edit the Web Query on an Excel Dynamic Worksheet with data from CRM 2016. This has worked in the past but has not recently. We follow the following steps. Navigate to an entity view in CRM Export as a Dynamic Worksheet to Excel Open the exported worksheet Click on the Data Tab - Connection Select the Workbook Connection Click on the Definition Tab The Connection type is Web Query, which cannot be changed Click on Edit Query We receive a standard Dynamics 365 error "Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions......." Any help appreciated. Thanks
↧
Forum Post: stop users enablng disabling personal tracking
Were trying to disable personal tracking for sales users due to personal emails being improrted to the crm. unfortunatly some users dont like this and are re enabling tracking. is there a way to ristrict the ability to turn on/off tracking to certain users?
↧
Blog Post: New Customization Experience in Dynamics 365
You may have noticed a few years ago the Power Apps logo was added to the Dynamics 365 Solution Customization website. This was a sign of things to come. Microsoft has redesigned the way customizations are done in Dynamics 365. You can view the new Customization experience by clicking the “Try New Experience” button in the message at the top of the Customization window. Otherwise browse directly to PowerApps through the menu or https://make.powerapps.com and then open the Solutions tab. Microsoft is changing Dynamics 365 to use the PowerApps Customization and will eventually phase out the classic Customization. If you haven't used PowerApps before, what is the difference? The new Customization UI is a giant leap from the classic UI, which has essentially been the same since CRM 2011. Now let’s compare the differences between the Classic Customization and the New Customization. Customization Solutions Classic: New: The UI is noticeably different with the menu on the left, the Dynamics 365 solutions are all located within PowerApps. An additional function is the Solution checker, which you can run to view the analysis of your solutions. This allows you to view a report of your components or code and check whether you are following best practices. You may receive warning or error messages relating to your Plugins, Web Resources or Workflows. Components Classic: New: The new UI is a lot cleaner than the classic. Instead of a navigation tree to each record you need to select the filter in the top right. Entities Classic: New: When customizing an entity, the navigation has changed from the Tree view to Tabs. Additionally, in the Data tab you can view live data from Dynamics 365 and interact with records like the Entity View. Forms Classic: New: The biggest changes are with the form editor. With cut and paste you can easily move fields, controls, sections or tabs around like a Word document. Instead of clicking “Change Properties” for a pop up to edit items on the form, it is easily accessed on the right panel just by clicking something like a field. Adding Fields or Components are now accessed from the left panel. Also, the Forms content is viewable in the Tree View. This is a visual way to see the layout of the Form. Fields Classic: New: Fields are added through a panel on the right, rather than a pop up. This makes for a better user experience. The changes to fields include: The menu has been cut down; removing “Field Security”, “Auditing”, “Appears on global filter as interactive experience” and “Sortable in interactive experience dashboard”. Note: Currently to modify these field settings you will need to use the Classic customization. “Data Types” have had an overhaul: Categories have changed “Single Line of Text” is now “Text”, “Multiple Lines of Text” is “Multiline Text”, and Image has been removed as an option. The Format field has been removed and is included in Data Types under a corresponding Category. Below shows the options previously available for “Single Line of Text”. The Data Type “Two Options” has icons added to indicate, which is Yes and No, even if the Label changes. Views Classic: New: Here is another drastically different change, this looks like the new form editor. The Left Panel is for adding fields, the Right Panel for changing the View settings. You can see data in the View, while editing it, which is very helpful when configuring settings like column width. Plus having an Undo and Redo button is a useful feature. This was a brief overview of the new Customization experience, now is the time to embrace change!
↧
Blog Post: MB 200: Microsoft Dynamics 365 Customer Engagement Core – OneNote Integration
I am creating a series of blog posts that collectively are designed to help anyone preparing for the Microsoft Dynamics 365 Customer Engagement Core exam. (aka MB-200) In this post I will look at concepts around OneNote integration. You can see below that we have a section of the exam which covers implementing integrations, within that we have a section regarding Office 365 and OneNote. I guess the first question might be, what is OneNote? (Although I hope you know the answer!) OneNote, as the name suggests is a product for taking notes. It is part of the office suite available in Office 365. Notes can be simple items of text but could also involve screen shots, audio or even video that relate to whatever subject is being covered. Meaning that OneNote offers a much richer interface than available within standard Dynamics 365 note taking. OneNote also supports co-authoring, allowing multiple people to collaborate on a single “document”. OneNote has a variety of clients to install locally, run on-line and even as apps on mobile devices. OneNote uses a concept of notebooks, each notebook can have sections and pages, Just like a real notebook! Note: OneNote also has a concept of section groups but this is currently not supported by the Dynamics 365 integration. Meaning you should only use sections and pages when integrating with Dynamics 365. You can then create and collaborate on OneNote documents using any of the supported clients. Maybe think of OneNote as an extension to the note taking capabilities in Dynamics 365 rather than a replacement. From the Timeline in Dynamics 365 it is possible to open OneNote notebooks in the context of the currently selected record. You do this from the “+” icon. Clicking the OneNote option will create a new notebook for this record. Or alternatively if a notebook already exists it will be opened. Tip: If you are familiar with the classic web interface for Dynamics 365 you may be aware that a separate tab used to show for OneNote in the social pane. (As shown below.) This older approach has been replaced in the new Unified Interface! OneNote integration uses SharePoint to store the notebooks. Because of this OneNote integration options can be found in the document management area of advanced settings in Dynamics 365. Prior to enabling OneNote integration each entity requiring the OneNote functionality must also already be enabled for document integration. An alternative approach to enable OneNote integration is to navigate to the entity in customizations and enable in the communication & collaboration section. Note: I have shown the classic approach to customizations below. The OneNote integration property is not currently accessible in the newer make.powerapps.com interface. If a OneNote doesn’t exist one is automatically created in SharePoint. Each record in Dynamics 365 will have only one notebook, which is shared across all users. (Hence the use of SharePoint rather than OneDrive for Business!) Clicking on the OneNote option in the Timeline will create a new notebook or open an existing one.. If you review the documents option on the entity you will be able to see the file(s) that makeup the OneNote being stored in SharePoint. (You access the “documents” option from the Related option!) This illustrates that SharePoint is required prior to integrating with OneNote. Also you should be able to see that the OneNote could be opened directly from SharePoint without opening Dynamics 365 if required. If you remove a Dynamics 365 record the associated OneNote notebook will not be removed from SharePoint. You’d need to remove the notebook manually from SharePoint. By default, Dynamics will create a separate document location and a separate OneNote notebook for each record viewed. Should you wish to share one notebook across multiple entities this can be achieved by manually editing the document location so that it points to one shared OneNote notebook location. As with SharePoint integration you need to be aware that Dynamics 365 access and SharePoint access (and therefore OneNote) are not directly linked. Permissions will need to be granted in the Dynamics 365 security model and SharePoint independently. You need to ensure users have access to both Dynamics 365 and SharePoint. It is also worth understanding that SharePoint and OneNote configuration does not form part of the Dynamics 365 solution file. When moving from development to production environments any configuration will need to be repeated in both environments. In this post I hope I have covered all of the major points needed for the MB 200 certification. But as always I strongly encourage you to gain some real world hands on experience.
↧
↧
Forum Post: RE: An error has occurred. Please return to the home page and try again. (on quick create form)
Hi, thís did work. That is, I changed it from No to Yes and the error was gone. But, what have I done now? Any other results that I should take account of?
↧
Blog Post: Microsoft Partners and CSPs Need Automated Billing Systems – Why Excel Isn’t Enough
If you’re in the business of generating recurring revenue like Microsoft CSP Partners and using Excel to handle your customer’s subscriptions and billing, you’re not alone. Dynamics 365 can easily be used to manage your sales and service, and with Work 365 you can manage recurring revenue and Billing automation for subscription sales. While Partner Center and Distributor portals are available, most Service providers still use spreadsheets to log and record the changes that are being made to subscriptions and services. These changes along with a combination of all the different invoices are used to invoice and bill a customer. This process can take hours or even days for teams of sales and accounting members to manually go through customer accounts and match up customer data in Dynamics CRM with the appropriate subscription changes in order to manually create and send out invoices. Most importantly this process is not scalable. Automating this process can save a service provider hundreds of employee hours that can be used to focus on value creation tasks around customer service and sales to grow the business. Billing automation solutions like Work 365, that are built on Dynamics 365 allow Microsoft Partners to grow their recurring revenue with these great features around billing automation: Bundling products and services into custom packages Automatically Creating invoices by calculating prorations, refunds, and renewals Automatically Sending and Collecting payment for invoices through Calculating monthly Sales commissions and incentives Integrating with accounting systems Enabling Self-Service scenarios for customers to directly provision and manage their services Work 365 is built on Dynamics 365 and has bi-synchronization with Partner Center, all subscription changes, billing, and payment status, and invoicing can be done directly from Work 365 with a click of a button, saving Partners and CSPS time and using multiple systems to keep their records in check. Watch our webinars to see how Work 365 can help Indirect and Direct CSPs automate and reconcile billing and invoicing. By Ismail Nalwala I am a Dynamics 365 enthusiast. I enjoy building systems and working with cross-functional teams to solve problems and build processes from lead generation to cash collection. Work 365 is a global developer of the Billing Automation and subscription application for Dynamics. Helping companies to streamline business processes and scale their recurring revenue. The post Microsoft Partners and CSPs Need Automated Billing Systems – Why Excel Isn’t Enough appeared first on CRM Software Blog | Dynamics 365 . Related posts: Microsoft Dynamics CRM vs. Salesforce – 5 Reasons Why Dynamics is the Better Value What Is a 360-degree View of Your Customer, Why You Need It, and Why Microsoft Dynamics CRM Is the Best Way to Get It Productivity platform? It’s not enough!
↧
Forum Post: RE: Difference between (real time) workflow error messages lay out
Hi, Can both screens pop up for the same conditions? For instance; the screenshot on the right is the as-is one, if Unified Interface is enabled, you'll see a different screen layout for the error, not really the one on the left though. Regards,
↧