Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Comments
http://www.pardaan.com/tag/nav-2013/
Recently I discovered that when attempting to Replace Table Objects In An NAV 2013 R2 Database I Received The Following Error Message “The table definition is invalid and cannot be validated”.
It Turns Out In NAV 2013 R2 There Is Setting Found Under
Tools à Options à Prevent Data Loss From Table Changes
- See more at: http://www.pardaan.com/tag/nav-2013/#st ... c6Opm.dpuf
The only way we managed to import the tables without disabling "Prevent Data Loss" was to go to the Properties of each field in the table, and within "CaptionML", remove the special characters.
Hope this helps some of you.
Cristian
I have removed the Swedish ML-caption but it didn't help so localization doesn't seem to be the culprit here
I can't force a schema syncronization, this is the error message:
Microsoft Dynamics NAV Development Environment
The server "nMASTER_2015" was unable to process the request. The application will close.
OK
www.nabsolutions.se
I have also NAV2013 R2 database and I am adding a new field (type: date) and when I want to save and compile the object I receive the error.
I have already changed same objects before and I did not get this error. At that time I was using German regional settings on the laptop where database and NAV DEV tools were installed. NAV database was build on WIN server using German regional setting.
Error first popped as I changed regional settings to US English in Windows 10, so I reverted it back to Germany, restarted computer and NSTs and then I could compile objects as expected.
Thank you
BR Damjan