CRM Blog

Wednesday, July 16, 2008 - Posts

Problems Running CRM 4.0 Reports Post-Installation or Upgrade, Even after installing Microsoft CRM Data Connector
by Shelley Lane 07.16.08

Comments    No Comments

When installing CRM 4.0 (or upgrading from 3.0) in an environment where SQL Server, SQL Reporting Services and CRM will all be on separate physical machines, you must use the Microsoft CRM Data Connector to bypass authentication issues. Once you’ve done this, your servers will all be able to communicate without issue and your reports will work swimmingly!

 

Well, almost. Recently, I encountered two separate instances (a new install and an upgrade, both using the Data Connector) where we had run all of the installs without any problems, but attempts at running any reports lead to the dreaded "Page Cannot Be Displayed" error.

 

In one case, the event log on the SQL Reporting Services server had several security audit failures. In there other case, there were no errors to be seen. However, both situations were the result of our Report Manager not being properly configured.

Follow these steps to verify that yours is configured correctly and, hopefully, save yourself some time.

  1. Open up Report Manager (http://SRSServer/Reports)
  2. Click on OrgName_MSCRM
  3. On the right-hand side, on the toolbar, click Show Details
  4. Click on the 4.0 folder
  5.  Then locate and click on MSCRM_DataSource
  6.  Verify that Connection Type is set to "Microsoft CRM Data Extension" and Connect using: is set to "Credentials supplied by the user running the report"
  7. Click Apply

 

Filed under:
Creating a 1:N Relationship with Parental Behavior causes "No Attribute" Error
by Zahara Hirani 07.16.08

Comments    1 Comment(s)

If you have tried creating a “1:N” relationship between a system entity and custom entity with the "Type of Behavior" property set to “Parental”, you most probably have also gotten an error when you try to save the system entity after updating its parent.

Let’s consider a Contact entity and a custom entity called Specialization. The relationship between Contact and Specialization is a “1:N” relationship with the "Type of Behavior" property set to “Parental”. Contact being a system entity already has a “1:N” relationship with the "Type of Behavior" property set to “Parental” with the Account entity.

So when you try to update the Contact's Parent Customer attribute and save, you are re-parenting the Contact. Since you have a relationship with "Type of behavior" set to “Parental” between the Contact and Specialization, CRM tries to re-parent the Specialization record with the updated Account object which it doesn't find. Hence the "no attribute" error.

To fix the issue, change the relationship between the Contact and the Specialization to “Configurable Cascading” and set the Re-Parent property to "Cascade None"; Save and Publish and your all set.

Now if you try to re-parent the Contact, CRM won’t try to re-parent the specialization record since the Re-Parent property is set to "Cascade None".

Filed under: