soapUI and SocketException with large data

I tested my WCF service with soapUI and wondered why I always got Socket Exception: Connection reset. I saw with debugger that my service returned what it should. The amount of data returned was big, and I had modified my web.config (maxReceivedMessageSize, maxBufferPoolSize, maxStringContentLength, maxArrayLength)  to allow large data.

After checking the trace files, it turns out I also need to add endpoint behavior to change the maxItemsInObjectGraph setting: http://stackoverflow.com/questions/3058202/wcf-service-datacontractserializer-maxitemsinobjectgraph-in-web-config

Links to Entites in Excel Generated by Metadata Document Generator for Dynamics CRM 2011

Metadata Document Generator for Dynamics CRM 2011 is a nice tool  you can create documentation of your CRM entites with.

Created Excel document is even nicer if you add links to tabs, so finding a specific entity is faster. This is how I did that (in Excel 2010):

1. I added new column to the Entities list -tab next to the Entity.
2. I used formula =HYPERLINK(CONCATENATE("#'";LEFT(CONCATENATE(A7;" ("; E7; ")"); 31);"'!A7"); A7)
3. I hid the original Entity-column

This formula can of course be applied to any list in Excel that corresponds to tab names.

Business rule vs. functional requirement

I'm taking a course in business analysis, and thought that requirements gathering would be the easy part for me, since I have been documenting and reading requirements before, but now I realize I really don't really get the difference between  a functional requirement and a business rule.

Wikipedia: "a functional requirement defines a function of a software system or its component. A function is described as a set of inputs, the behavior, and outputs. Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describing all the cases where the system uses the functional requirements are captured in use cases." 

BABOK defines functional requirements as "the product capabilities, or things the product must do for its users."

Wikipedia: "A business rule is a rule of a business, company, or corporation. It is a rule that defines or constrains some aspect of business and always resolves to either true or false. Business rules are intended to assert business structure or to control or influence the behavior of the business. Business rules describe the operations, definitions and constraints that apply to an organization. Business rules can apply to people, processes, corporate behavior and computing systems in an organization, and are put in place to help the organization achieve its goals."

The course material describes business rules as obligations concerning actions, processes, and procedures that define, and possibly constrain, some aspect of the business. 

Ok, now it's starting to make sense to me, this is my conclusion:
- Functional requirements often start with "the system shall.." or "the system must..", as they state what the system must be capable of doing,

 - Business rules simply state what rules must be followed,  by the people, processes or systems.