SharePoint 2010 introduced a quantum leap forward with the introduction of Visual Web Parts development integration with Visual Studio 2010. Most developers that have worked with SharePoint for any length of time are familiar with hosting custom ASPX pages inside SharePoint web parts. Doing so allows us to present robust applications and interfaces inside the SharePoint portal and fully utilize all of the robust security features and other goodies that come with SharePoint. The introduction of Visual Web Part development eliminates the need for separate web sites and pages since the custom web part becomes an integrated component of the SharePoint application. All of this come without having to use STSDEV, VSeWSS, or the like. We can simply build the web part right inside Visual Studio and click Deploy! A really great feature is the ability run & debug right from Visual Studio without any special configuration required. All of this greatly simplifies and expedites the development of custom enhancements to a SharePoint application and is no doubt Microsoft’s response to the fact that the number of SharePoint developers continues to grow, as does the number of SharePoint implementations.
As the Dynamics CRM product evolves to provide more flexibility and extensibility for the user, changes to the underlying object model are inevitable. Microsoft must provide more robust and flexible entity attributes that allow users to customize CRM 2011 to meet their specific needs. Fortunately for developers, the programming model has been changed to use native .NET types whenever possible. Often, developers need to capture an entity's attribute values to perform some custom function or action using a plugin. This might include updating other entities or even creating new entities based on the values derived from the base entity.
In CRM some times you need to add custom pages to add functionality that does not natively exists. Here is an example of a product edit grid iframed in the opportunity entity
In MS CRM 4.0 any field changes made that are enabled will be save. Lets say on the Account form you have a picklist that will display the following in an IFrame.
Map to Account Address
Primary Contact Information
Page to ERP showing Credit Stats.
When you change the CRM picklist controlling the IFrame CRM will change to IsDirty (asking you to save or not on exit). You really probably don't want to allow of force the user to save every time they lo ...
In MS CRM 4.0 have you ever wanted to rename or remove Left Nav links on an entity only to find the OnLoad script fails when trying to use the preview function on the form designer?
In many CRM installs companies prefer to not use the Microsoft CRM product catalog so that Write-In Products is really the list of products (on a Quote for example) and Existing Products never has anything listed under it. Thus they would prefer to eliminate the Existing Products link ...
In MSCRM 3.0 to hide system view just took a simple trick to the system. In MSCRM 4.0 Microsoft removed the work around now not letting you get rid of unused or unwanted system views. Doing some searches I found 2 different System View Hiding Plugins but I did not Like having to recompile or edit XML outside of CRM to get rid of the View.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.