WOW! I'm sooooo happy when I receive such deterministic errors.
After saving an account, this message popped up. And you guessed it - it appeared just SOMETIMES!
After a little of SQL profiling i found the reason:
I extended the account's address1_line1 field from 50 to 100 characters. After saving the account, CRM automatically creates/updates also the customeraddress entity.
Solution:
Extend the customeraddress entity, extend attribute line1, match the length to length of the account address line.
skip to main |
skip to sidebar
MS CRM blog for developers
Subscribe
About Me
- Dejan Dular
- Novo mesto, Slovenia
- .NET and Microsoft CRM developer, MCP, SQL enthusiast, nature lover and loving father Follow me on twitter: @dejandular
Blog Archive
-
►
2017
(2)
- ► 16 July - 23 July (1)
-
►
2016
(3)
- ► 20 March - 27 March (1)
-
►
2009
(6)
- ► 12 July - 19 July (1)
- ► 22 March - 29 March (1)
-
▼
2008
(5)
- ► 29 June - 6 July (1)
- ► 25 May - 1 June (1)
- ► 2 March - 9 March (1)
-
►
2007
(24)
- ► 29 July - 5 August (1)
- ► 24 June - 1 July (4)
- ► 3 June - 10 June (1)
- ► 13 May - 20 May (1)
- ► 18 March - 25 March (1)
- ► 11 March - 18 March (6)
4 comments:
My console application takes care of transferring data from Client's dbase to MS CRM. Talking of the contact entity address_line1 entity is an nvarchar field with 2000 chars and in the client's dbase its datatype is varchar(2000). on calling service.Create() method, I get this error: "Generic SQL error".
Can anyone help, where am I missing something?
Thank you for that tip! I have been struggling with the same thing.
Did it change the field width for that field in the FilteredAccount view as well??
FilteredAccount is a view, so the field length is "updated" automatically from AccountBase table.
I did this eventually but when I looked at the definition of the FilteredAccount view it still showed width 50.
I was concerned but I found that when I queried the view I got the data in the table even if it was more than 50 characters.
Post a Comment