1

Closed

A primary entity column cannot have a dot in its nameDetail

description

Hi Tanguy,
 
Thanks for the tool. I'm a newb on 2011 and this is going to save me a massive amount of time.
I do have a problem that I thought I should report to you.
 
I got an error when selecting a view on cases. See Below.
 
I checked the view afterwards and it has a GUID instead of a field name.
I've attached a screen shot.
This field should have been Customer (Account) Account Name.
 
I don't have any more info but will see if I can narrow it down to some customization I've done.
 
Steve
 
 
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: A primary entity column cannot have a dot in its nameDetail:
<OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
<ErrorCode>-2147220970</ErrorCode>
<ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
<Message>A primary entity column cannot have a dot in its name</Message>
<Timestamp>2011-06-02T12:07:52.2284897Z</Timestamp>
<InnerFault i:nil="true" />
<TraceText i:nil="true" />
</OrganizationServiceFault>

file attachments

Closed Jul 27, 2011 at 7:16 AM by tanguy92

comments

tanguy92 wrote Jun 24, 2011 at 7:09 AM

Hi Steve,
Sorry for the late response, I thought codeplex was notifying me when an issue was reported which doesn't seem to be...
I'll look at your problem as soon as possible

wrote Jun 24, 2011 at 7:12 AM

tanguy92 wrote Jun 24, 2011 at 7:12 AM

Steve,
The screenshot is not visible... can you attach it in a new comment?

wrote Jun 24, 2011 at 7:22 AM

tanguy92 wrote Jun 24, 2011 at 7:23 AM

Ok, I tested the same customization as yours and I didn't get any error (Screenshot in attached files)

Are you sure to use the latest version available?

Mixer63 wrote Jul 6, 2011 at 4:20 AM

Steve, I encountered the same problem with views as you reported. I think it was a legacy left from CRM 4.0 migration. I fixed it by editing the All Active Cases and All Resolved Cases views and deleting the last column which caused the problem (you will see in edit mode, that the column is already highlighted as incorrect).
Hope it helps.
Anthony

pieeetr wrote Jul 6, 2011 at 2:53 PM

I'm getting the same problem. Seems like it only occurred on fields inserted from a related entity. However I tested on version x.25, I'll try version 26 in a minute.

pieeetr wrote Jul 6, 2011 at 3:00 PM

I tried version x.26 too, same error for me. Yes, in edit mode I can see that the columns are corrupted, but the source view works perfectly. When I manually add the same columns to the destination view as those that are in the source view.. it works fine. But it doesn't work when I try to do it with the view replicator.

I haven't had any problems with this tool before, but maybe that was because my views didn't have any fields from related entities?

tanguy92 wrote Jul 7, 2011 at 9:01 AM

Ok guys,

I tried to reproduce your problem but can't succeed...

What I've done:

Customization:
  • Create a view with a related entity column (entity: contact, columns: fullname, (account) account rating code )
  • Create a view with only the primary attribute (entity: contact, columns: fullname)
  • Publish
Run the tool:
  • Select the view with the related entity attribute
  • Check the view without the related entity attribute
  • Save changes
  • Publish entity
Customization:
  • Open the view that was changed using the tool
  • Here, I get no error, no warning, everything works well
Can you try to reproduce this exact procedure?

wrote Jul 26, 2011 at 7:31 PM

edwardsdna wrote Jul 26, 2011 at 7:31 PM

Hey Tanguy,

I'm using the replicator with CRM Online today and am seeing this issue. I haven't had the time to tell you exactly why it is happening but at first glance it looks like it is throwing an error on some columns that it is trying to remove from the view. If you open the view, you will see the column that the replicator tried to remove as it will show in the view with a string of characters and the view has a notification to remove the column. Once the column is removed from the view, save and publish, everything works again. You can contact me directly if you want more information. I was working in CRM Online

Thanks for the great tool, I love it and I blogged about it :)

edwardsdna wrote Jul 26, 2011 at 8:00 PM

so this time I payed closer attention when I loaded the Opportunity entity and selected the View for replication. It does look like it is a related entity issue. Below is the xml that displayed when I selected the Open Opportunity view to replicate. As you can see, it assigns some funky value to a couple of the related entity cell names. I hope this helps!

<grid name="resultset" object="3" jump="name" select="1" icon="1" preview="1">
<row name="result" id="opportunityid">
<cell name="customerid" width="150" />
<cell name="a_34e7bb29d7d04dcb985d78a992c283cc.customertypecode" width="100" disableSorting="1" />
<cell name="ownerid" width="100" />
<cell name="estimatedclosedate" width="125" />
<cell name="estimatedvalue" width="100" />
<cell name="closeprobability" width="100" />
<cell name="opportunityratingcode" width="100" />
<cell name="a_34e7bb29d7d04dcb985d78a992c283cc.address1_stateorprovince" width="100" disableSorting="1" />
<cell name="a_34e7bb29d7d04dcb985d78a992c283cc.address1_postalcode" width="100" disableSorting="1" />
</row>
</grid>

edwardsdna wrote Jul 26, 2011 at 8:18 PM

by the way, the interesting thing is that the issue doesn't affect all views if you go ahead and select to change the views then publish the changes.

For example, in regards to the Opportunity entity Views, I proceeded with updating all the views even though the xml did not not load as expected. I then published the changes from the replicator and checked the Opportunity views. Several of the views were updated with the correct cell names and only a few had errors.

Some of the views that had the error I showed in the screenshot are the Opportunity Lookup View, and Opportunity Opened Last Week. So if you want to test this, you can update the Open Opportunity View and add the Relatioship Type from the related account entity. Save the view and publish, open the replicator and look at the Open Opportunity View to see if the xml for Relationship Type cell shows the unexpected characters.

tanguy92 wrote Jul 27, 2011 at 6:46 AM

Hi donna,
Many thanks for the feedback (and the blog post, too :))

I'll try again to repro but didn't succeed last time...

For information, the "funky" value represent the link-entity alias in the fetchxml part of the view

wrote Jul 27, 2011 at 7:16 AM

Resolved with changeset 7759.

wrote Feb 14, 2013 at 7:13 PM

wrote May 16, 2013 at 8:59 AM

CRMLarry wrote Apr 28, 2014 at 5:45 PM

Thanks, Tanguy. I had the same problem. Your post saved me a lot of time and aggravation.