web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Why does the Document No. field in the Sales Transaction Entry form only have a maximum length of 17 characters, while the SOPNUMBE field in the SOP10100 table has a maximum length of 21 characters?

(0) ShareShare
ReportReport
Posted on by 280

Hi,

The Sales Transaction Entry form only allows to enter a maximum length of 17 characters for the Document No., whereas the SOP10100 table and taSopHdrIvcInsert stored procedure allow a maximum length up to 21 characters for this field.
Is there probably a reason for this?

Please help me answer this question. Thanks in advance!

Khang

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    on at
    RE: Why does the Document No. field in the Sales Transaction Entry form only have a maximum length of 17 characters, while the SOPNUMBE field in the SOP10100 table has a maximum length of 21 characters?

    Hello:

    dynamicsgpland.blogspot.com/.../exceeding-econnect-char-field-lengths.html

    Cheers!

    Sanjay

  • Suggested answer
    Olaf Laos Profile Picture
    1,890 on at
    RE: Why does the Document No. field in the Sales Transaction Entry form only have a maximum length of 17 characters, while the SOPNUMBE field in the SOP10100 table has a maximum length of 21 characters?

    There is the keyable length of 17 and the storage size of 22

     

  • Suggested answer
    Mahmoud Saadi Profile Picture
    32,738 on at
    RE: Why does the Document No. field in the Sales Transaction Entry form only have a maximum length of 17 characters, while the SOPNUMBE field in the SOP10100 table has a maximum length of 21 characters?

    This case is not limited to the sales transaction field ID only, since Dynamics Dictionary has a field definition corresponding to the SQL field definition. 

    You cannot change at the SQL level, any mismatch between the definition in SQL and Dynamics.dic will cause a critical error. Which is why e-connect (as explained in the post provided by Sanjay) wil silently truncate the length to the correct corresponding field length restricted on the interface level.

    Hope this helps, 

  • Khang Profile Picture
    280 on at
    RE: Why does the Document No. field in the Sales Transaction Entry form only have a maximum length of 17 characters, while the SOPNUMBE field in the SOP10100 table has a maximum length of 21 characters?

    Hi Sanjay,

    Thank you for replying. I already read this link before. But I still want to know why GP has a bigger field size in DB for the Document No..

    Khang

  • Suggested answer
    Community Member Profile Picture
    on at
    RE: Why does the Document No. field in the Sales Transaction Entry form only have a maximum length of 17 characters, while the SOPNUMBE field in the SOP10100 table has a maximum length of 21 characters?

    Why  -  Microsoft experts would have a response, allowing

    1)  e-connect to store to the full compliment of 21 characters

    2)  Showing full compliment of 21 in look up windows

    3)  But allowing only 18 characters at entry window ...  

    Cheers!

    Sanjay

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans