Today we got one more product bug in case of New Form Rendering The Add New Button for OOB Inline Edit Sub grid works properly, however for a new custom sub grid it doesn’t work. The same works properly in case of Legacy Form Rendering. Clicking on + button opens the new form for Opportunity Product … Continue reading "Bug in New Form Rendering CRM 2016 Update 1 – Add New button not working for Opportunity Product Sub Grid in Opportunity Form."
While trying to import a managed solution to our test environment we got the below error “Cannot update a report from a template if the report was not created from a template”. We got this error on one specific report. Removing that particular report from the solution and trying the import again fixed the issue … Continue reading "Cannot update a report from a template if the report was not created from a template error while trying to import solution in Dynamics 365"
Continuing with our posts regarding the recent release of Dynamics 365, next up is discussing the new Visual Process Designer. Additionally, head over to the CRM Roadmap site, or the CRM What’s New site to see more of the features that have recently gone live. Visual Process Designer With Dynamics 365 for Sales, a new drag and drop WYSIWYG designer has been created for creation and management of business process flows, task flows, and business rules. When you open up the proc
Applies to: Microsoft Dynamics CRM Online 2016 Update 1 I am pleased to announce the release of Microsoft Dynamics CRM Online 2016 Update 1 Performance Benchmark which is currently available for download, from Microsoft Download Center. This is the second whitepaper being published, as promised in the CRM blog a few weeks ago. The initial...
Recently in our project we tried implementing solution upgrade to delete some of the components from the existing managed solution. https://nishantrana.wordpress.com/2016/10/16/how-to-delete-components-from-managed-solution-in-dynamics-crm-2016-without-using-holding-solution/ However, we kept running into SQL time out issue and it didn’t work for us. Finally we raised product support ticket for it and eventually the product support team increased the SQLCommandTimeout to 5 … Continue
Today's blog post was written by Brendan Landers, VP of Consulting at Sonoma Partners.Microsoft has released a number of new tools recently that are very interesting but have left a number of us asking, “What does that mean for CRM?" While I’d imagine a more official roadmap will be forthcoming, we wanted to convey our thoughts on these tools and how they may impact your CRM program or project.These tools are all part of the Office 365 suite and were recently made available prior to
Applies to: December 2016 Update for Microsoft Dynamics 365 (online) and December 2016 Service Pack for Microsoft Dynamics 365 (on-premises) This year brought major changes to the Microsoft CRM platform—even its name changed from Dynamics CRM to Dynamics 365. Dynamics 365 still provides all the familiar capabilities of Dynamics CRM, but now also aims to...
Today's blog post was written by Keith Mescha, Principal Architect at Sonoma Partners.Here at Sonoma, we are a big fan of KingswaySoft’s tools for data migration to Dynamics 365 and Salesforce. We use SQL Server Data Tools and SSIS all the time for data migrations and integrations to CRM for our clients. The tool set they provide is an add-on that allows us to quickly read and write data from the cloud. In one recent migration project, we ran into an odd issue that took a bit to figu
While trying to import solution to our test environment from our dev environment we got the below error “Crm Exception: Message: Customer lookup [CustomerId] is invalid. Customer lookups can only be associated with 1 Account and 1 Contact” The way we got it fixed Unzip the solution and open customizations.xml file Remove all attributes with … Continue reading "Crm Exception: Message: Customer lookup [CustomerId] is invalid. Customer lookups can only be associated with 1 Accou
Recently we blogged about the functionality of the new editable grid in the Dynamics 365 release. One thing we pointed out in the post is that the editable grid doesn’t respect read-only fields on the form. For example, if I have the Email field on the Contact form set to read-only and I use an editable grid for a Contact view that contains the Email field, it will allow the Email field to be editable. One way to make the field read-only in the editable grid as well, is to write cu