Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics AX (Archived)

Custom EDT - Problems after string size increased

Posted on by 500

I have a custom EDT which I am using within Purchase orders and it was 60 characters long.

I've changed it to 4000 characters, done a full data synchronisation (from data dictionary), closed the client, deleted the AUC client files and restarted the AOS.

All of the tables appear to have 4000 characters in the AOT and also aligned in the SQL database but I am getting errors when doing various operations.

Simply opening up the PurchTable from the AOT and filtering on the affected field causes a database error:-

Cannot select a record in Purchase orders (PurchTable).
The SQL database has issued an error.

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

Also, I get the same errors trying to run the modified SSRS Purchase order confirmation report.

Does anyone have any known solution or suggestion?

Thanks

*This post is locked for comments

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,280 Super User 2024 Season 2 on at
    RE: Custom EDT - Problems after string size increased

    Hi MGP,

    I have verified the answers for you now. That is the reason why I did ask if your issue had been solved. You can't mark your own answers as verified.

  • Verified answer
    _MGP Profile Picture
    _MGP 500 on at
    RE: Custom EDT - Problems after string size increased

    Yes a shorter max string length resolved the problem but it's weird that AX 2012 doesn't accept the SQL Server limit of nvarchar(max) on a table field. Especially as it does successfully sync the AOT with the SQL table defintion.

    Btw I would accept the answer on the forum but the "Did this answer your question?" buttons are not visible (because it was my suggestion?!)

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,280 Super User 2024 Season 2 on at
    RE: Custom EDT - Problems after string size increased

    Hi,

    So, you were able to solve this error yourself now?

  • Verified answer
    _MGP Profile Picture
    _MGP 500 on at
    RE: Custom EDT - Problems after string size increased

    Having read this post https://community.dynamics.com/ax/f/microsoft-dynamics-ax-forum/177918/invalid-precision-value-error

    I decided to reduce the limit to 1000 characters and simply by synchronising the database it worked.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans