6,071
In reality, customers need to keep more sales information different from provided by system. NAV 2013 sales header standard fields already consumed 65% (around 5238/8000 bytes). Beside inactive some fields or use additional table solutions, is there any better way to solve this issue? Will this limitation be broken in next version?
*This post is locked for comments
Thanks Jonathan and Tharanga!
I would like to compare existed solutions for additional tables and blob field. Please let me know any blogs already implemented them!
This is a limitation with SQL because SQL page size is a 8000 bytes. As per my understanding best solution is to use a separate table and link it with your primary table. In that way you do not have to go through a big hassle in retrieving data.
hi,
as you mentioned: additional tables with (foreign) key "Document Type", "No." is a good idea.
one additional idea: save data in xml data structure and save it compressed into blob field (not very fast)
list of limitations:
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (