tag:blogger.com,1999:blog-3101394961765670978.post4699789276354826602..comments2023-05-30T04:08:26.864-04:00Comments on CRMScape: A Couple Data import issuesMark Kovalcsonhttp://www.blogger.com/profile/05363028899186950966noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-3101394961765670978.post-81432020770891218632009-08-06T11:53:34.181-04:002009-08-06T11:53:34.181-04:00You are probably correct. Before CRM 3.0 there wer...You are probably correct. Before CRM 3.0 there were issues deleting entities and fields that caused problems after the upgrade. As of CRM 3.0 this should no longer be an issue.Mark Kovalcsonhttps://www.blogger.com/profile/05363028899186950966noreply@blogger.comtag:blogger.com,1999:blog-3101394961765670978.post-73829406463965132912009-08-06T11:19:59.895-04:002009-08-06T11:19:59.895-04:00Yes, I think I've zeroed in on it a bit more. ...Yes, I think I've zeroed in on it a bit more. Let me see if I can make sense of it here.<br /><br />I found the issue using the following SQL (for Contacts):<br /><br />SELECT<br />somepicklist,<br />somepicklistname,<br />COUNT(*)<br />FROM yourcrmdb.dbo.FilteredContact<br />GROUP BY somepicklist, somepicklistname<br />ORDER BY somepicklist<br /><br />If there are any rows that have a non-null value in the first column (i.e., a pick list integer value) and null in the second (the pick list display value), that's the issue. To find the specific entities with that problem, I then used the following SQL (for Contacts):<br /><br />SELECT<br />'http://yourcrmurl/sfa/conts/edit.aspx?id=' + CAST(contactid AS VARCHAR(50)) AS URL,<br />fullname AS Name,<br />somepicklist<br />FROM yourcrmdb.dbo.FilteredContact<br />WHERE somepicklist IS NOT NULL AND somepicklistname IS NULL<br />ORDER BY fullname<br /><br />We've been on CRM since 1.2, and we're now at 4.0 and encountered the problem due to the new API throwing the validation errors, per your post (which was helpful for researching our issue - thanks!). My supposition is that a prior version of CRM allowed for the deleting of pick list values from a pick list attribute while still having those values populated in existing entity instances, and that when we were deleting those pick list values we didn't do a good job of doing an advanced find and reassigning the pick list to valid values before deleting the obsolete values. Does that make sense?Jim Lhttps://www.blogger.com/profile/02634460171128306060noreply@blogger.comtag:blogger.com,1999:blog-3101394961765670978.post-17967428046518726032009-08-06T10:44:21.514-04:002009-08-06T10:44:21.514-04:00That's an interesting issue that I haven't...That's an interesting issue that I haven't seen. Could you post what you find the problem to be?Mark Kovalcsonhttps://www.blogger.com/profile/05363028899186950966noreply@blogger.comtag:blogger.com,1999:blog-3101394961765670978.post-6169534577256251502009-08-06T10:29:24.849-04:002009-08-06T10:29:24.849-04:00FYI, we get the pick list errors when we have pick...FYI, we get the pick list errors when we have pick list values that have a null display value. Still trying to chase down how those can happen since those pick list values don't show up in either the pick list itself nor in the valid attribute values under the entity.Jim Lhttps://www.blogger.com/profile/02634460171128306060noreply@blogger.com