When I attempt to generate a datasource model I get the following error messages: ------------------------------------------------ More than one item in the Entity 'Customer' has the name 'Customer Merge Custs'. Item names must be unique among immediate siblings. (DuplicateItemName)More than one Field in the Entity 'Customer' has the name 'Customer Merge Custs'. Field names must be unique within an Entity. (DuplicateFieldName)More than one item in the Entity 'Pricing Service Layout Detail' has the name 'Pricing Service Extensions'. Item names must be unique among immediate siblings. (DuplicateItemName)More than one Field in the Entity 'Pricing Service Layout Detail' has the name 'Pricing Service Extensions'. Field names must be unique within an Entity. (DuplicateFieldName)--------------------------------------------------- Examining any of the above tables in SQL Server Management Studio does not reveal any duplicate column names. In fact, 'Customer_Merge_Custs' does not appear to be a column in 'Customer' nor does 'Pricing_Service_Extensions' appear in 'Pricing_Service_Layout_Detail'. As an experiment, deleting the table 'Pricing_Service_Extensions' and regenerating did make the two associated messages go away. Steve P.

I figured this out. If you have two columns like this BusinessSectorId and BusinessSector the schema generator removes Id from the first column and thus creates a duplicate name with the second column. I added some extra characters to the second column and it resolved the issue.

I have the same error when generating a model. I have two columns Vendor and VendorID in the table. I don't want to change the column names and all my stored procs. Is there a better solution to this or am I locked out of reporting services over this for good?

I found a workaround - instead of having the ReportManager or SQL Server Mgmt Studio autogenerate the model i used the Report Model Project in BI Studio. I created a report mode project with datasource, dataview and report model using the wizards for each. The error came up again and I could not deploy the project to the reporting server. However, the report model that was created allowed me to navigate to the entity (table) in question and rename the field (from Vendor to VendorName). The error then went away when I retried to deploy and worked fine.