In a recent post I wrote about being careful about what names you give your Entities to prevent them from conflicting with other assemblies or classes that are used by the SalesLogix Web application. On a similar note, I thought I should share another potential conflict that occurred recently. We had a client you had a field in an existing table called EntityType. This became a problem once we tried to create a QuickForm using this field within an entity. The problem is that the QuickForm auto-generates a method called EntityType when the form is created. If your page also has a bound field to a property called “EntityType” you will receive an error like “The type ‘ASP.QuickFormName’ already contains a definition for ‘EntityType’”.
Again, keep in mind potential naming conflicts and be prepared to adjust your entity model, as needed. In my case I simply added an underscore to the entity property to change it from “EntityType” to “Entity_Type”. You would also have to change any controls named EntityType that are on QuickForms.
