NAV2018 Extensions OnPrem - Same field no.

airam
Member Posts: 91
Hello,
I published two extensions for the same table (User Setup) with two separate additional fields, both using the same field number. No errors were initially given, but now, whenever I try to open the User Setup table or any tables related to it, NAV crashes.
I have since renumbered the field numbers in both extensions to ensure they are unique and marked both duplicate fields as ObsoleteState = Removed. However, NAV continues to crash whenever I attempt to access the affected pages or tables. Unfortunately, this issue is occurring in the Production Environment because one of the extensions was not published on the Sandbox, so no errors appeared there.
I am looking at these options
1. Manually delete the fields from SQL
2. Change the "schemaUpdateMode" to ForceSync (not sure if all the Extensions data will be lost, if yes, this not an option)
Any help would be much appreciated.
Best Regards!
I published two extensions for the same table (User Setup) with two separate additional fields, both using the same field number. No errors were initially given, but now, whenever I try to open the User Setup table or any tables related to it, NAV crashes.
I have since renumbered the field numbers in both extensions to ensure they are unique and marked both duplicate fields as ObsoleteState = Removed. However, NAV continues to crash whenever I attempt to access the affected pages or tables. Unfortunately, this issue is occurring in the Production Environment because one of the extensions was not published on the Sandbox, so no errors appeared there.
I am looking at these options
1. Manually delete the fields from SQL
2. Change the "schemaUpdateMode" to ForceSync (not sure if all the Extensions data will be lost, if yes, this not an option)
Any help would be much appreciated.
Best Regards!
0
Answers
-
Can you not delete the fields in extensions and redeploy them?United Kingdom0
-
thanks for your reply, however even with both fields deployed, NAV is crashing because they both have the same Field No. (in separate extensions), can't renumber as it gives an error..0
-
You have to renumber one and forcesync is it,United Kingdom0
-
unfortunately ForceSync is not available in NAV2018, so the only solution I am seeing at this stage is to remove the fields directly from SQL. anyone tried this already please?0
-
really forcesync is not available in NAV2018? I think it isUnited Kingdom0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions