Invalid precision value error

(0) Share

Report

Posted on by psined

I'm getting a native SQL error when trying to insert into a custom table called "MyTable". The custom table contains the following fields:

RecId parentRecId;
Guid entryKey;
MyEntryType entryType; // custom enum
Str500 summary;
Str4000 detail;

Other than the above my custom table has "CreatedDateType" system field turned on.

I got the table synchronized + the the entire DataDictionary AOT node synchronized.

I'm using a job with the following code to insert one record in to the table:

MyTable table;
table.initValue();
table.parentRecId = 5637144583;
table.entryKey = str2guid("{FFB111CB-AF74-4857-8E97-B45440E48336}");
table.entryType = MyEntryType::Type1;
table.summary = "this is a short summary";
table.validateWrite();
table.insert(); // this is where the error strikes

The error I get is this:

SQL error description: [Microsoft][SQL Server Native Client 11.0]Invalid precision value

Any idea what else could be wrong?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Martin Dráb 237,807 Most Valuable Professional on at

Like (0)

Report

Does it depend on some particular field? Play with it a little bit, it might reveal something useful.

It's off-topic and I understand it's a just sample code, nevertheless calling validateWrite() and ignoring its return value is an anti-pattern. If it returns false, either skip insert() or throw an exception.

Was this reply helpful? Yes No
Martin Dráb 237,807 Most Valuable Professional on at

Like (0)

Report

Just a wild guess, but can't Str4000 be the culprit? What if you use a shorter string?

Was this reply helpful? Yes No
psined on at

Like (0)

Report

Yes, the "detail" column appears to be the culprit. It was actually created in the table via drag-dropping a custom string EDT with length 4000 onto the table.. I can certainly try a narrower field, but in my case the detail may exceed that length, so I need a larger buffer. Sounds like AX only gives choice for either 1000 chars max or Memo type on a field. How would one go about adding an EDT for a Memo datatype? Is it at all possible?

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,807 Most Valuable Professional on at

Like (0)

Report

Actually, there is a suspiciously close limit in SQL Server: nvarchar [ ( n | max ) ] - Variable-length Unicode string data. n defines the string length and can be a value from 1 through 4,000.

Yes, you can create your own memo EDTs. Create a string EDT and set StringSize = Memo from the drop-down (if I remember it correctly). Or just use or copy and existing type, such as Notes.

Was this reply helpful? Yes No
psined on at

Like (0)

Report

Hi Martin, thanks for your help. Setting the custom EDT length from 4000 to "Memo" has fixed the problem.

Surprisingly, while adding a string column to a table with length above 1000 chars results in an "Illegal property value" error, AX is perfectly happy when I define a string EDT with 4000 and then drag-drop it on to a table - during synchronization AX even creates a proper NVARCHAR(4000) data type in SQL.

Was this reply helpful? Yes No

Community site session details

Invalid precision value error

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates

Community site session details

Invalid precision value error

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates