One of the issues that CRM had was how to filter records in a lookup control that is dependent on another control on the form. An example of this would be if I use the account and contact entity and have a connected entity in between such as maybe a position.
Microsoft has released the much awaited Microsoft Dynamics CRM 2011 public beta, formerly known as V.Next today. Microsoft Dynamics CRM 4.0 was a huge jump in enterprise scalability, performance and a true multi-tenant architecture. Microsoft Dynamics CRM 2011 takes that release and builds in usability, a ribbon like interface, more of a flat User Interface that requires fewer clicks and better visualizations.
If you are using Forms Based Authentication for you SharePoint site you might encounter the site displaying a user name such as “i:0#.f|sql-membershipprovider|username” instead of just “username”.
When trying to install the Microsoft Dynamics CRM for Outlook client on a Terminal Services computer, the following error is received:
“Microsoft Dynamics CRM 4 for Outlook cannot be installed on a computer where Microsoft Exchange Server versions prior to Exchange Server 2007 are installed.”
The ribbon in SharePoint 2010 is visible to users regardless of the user’s permission. Even for anonymous users it will show up (just with the Navigate Up button). In order to hide the SharePoint ribbon from users, we will need to modify the master page or pages that are available to users without permissions.
iPhone 4 went loudly into the streets and with reports of a number of critical issues in the design of the device. Some conflicting reports say that the problem is in the device-level design and some users did not see any problems with reception.
When implementing Forms Based Authentication (FBA), SharePoint retrieves the tp_title field from the UserInfo table in the WSS_Content* database to display the name of logged in user.
The System.Management.Automation assembly allows the exeuction of Powershell commands against Exchange server.
Although, it would seem that the same code would be able to run for both of the versions of Exchange Server, two different codebases are required. The reason for this is that Exchange 2007 (SP1) supports only local Powershell, and Exchange 2010 uses remote Powershell.
When using SQL Server logins to connect to a database that has just been restored, most likely the following error will appear: Login failed for User ‘username’
Meteorologists possess the uncanny ability to be almost right almost all of the time. Now that doesn’t always help when you’re planning the company picnic, but reports of a 70% chance of precipitation does, at the very least, encourage the party planner to rent a tent. What weather men and women are unable to do, however, is predict weather trends for the years ahead. (Global warming controversy notwithstanding. . .)