Finally, after a long wait, editable grids are here. With the release of the editable grids, there have been some changes implemented not only on the grid, but also on the way that data that is manipulated from the form. There is now a single set of code that can be run from both the form and the grid, so that you don’t have to write your code separately for each.
Our CRM Exchange Sync with support for Microsoft Dynamics 365 has just been released, now with additional functionality and support for additional environments. The CRM Exchange Sync application provides the capability of synchronizing between Microsoft Dynamics CRM Marketing Lists and Contacts with Exchange Distribution Groups, Mail Contacts and Mail User records.
When developing web resources that are embedded on a CRM form, you sometimes have to call a function on the parent form. In the past (prior to CRM 2016), you could simply call the function by using parent.myFunction(), however that logic does not work anymore.
Editable grids were introduced as a new custom control in Microsoft Dynamics 365, which provide inline editing capabilities for data within the main grid and form subgrids for web and mobile clients. The editable grids include support for grouping, sort and filtering data within the grid, so that we don’t have to switch between records and views.
The telephone fields in account, contact and lead entities do not really come with any formatting rules for particular countries. The phone field format setting might resolve some issues, but not all of them.
Recently I had this question come up, and wanted to discuss the difference between closing an incident (Case) as resolved, or closing an incident as cancelled. There are a few other options, but we will focus on these two.
Sometimes you write applications that contains some logic, that require you to create steps for your plugin based on other entities. For example, if you have an AutoNumber solution, you can create a plugin step for a particular entity every time you create a new AutoNumber record.
In a recent post we showed how to retrieve all the team members of a particular record. This was different then using the default My Team Comments view, and we showed the relationship that is needed.
We recently had a requirement to add an approval process to an entity in CRM. This was a custom entity (Comment), where most of the fields were prepopulated from the web, but had a response field that had to go through multiple layers of approval/review. The review process was once the comment was received it would be assigned to a responder, which would then go through manager, legal and director approvals.
We recently got into a situation where a client wanted to have a view that will display all the records of all the users that belong to the same team as the logged in user. Originally we thought it would be easy, but it happens to be slightly more complex.
