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
- 262 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
Options
Orphan extension - cant import company
Noeline
Member Posts: 54
Hi
We have a client on BC 21 - 2022 release wave 2 on prem, with a UAT database and a Production database. Recently we created a new instance and forgot to disable designer, and a user added a field to a page in designer. When we noticed it, we uninstalled, unpublished, and disabled designer. We now have a situation where we want to import a new company from the UAT to Production, and that extension is causing an error. It is not listed under extensions, nor under Get-NAVAppInfo.
After much research which yielded few results I scratched around in SQL and found the extension in $ndo$navappschematracking. Unlike the other extension which have been unpublished, that one still has a value in appstructuredtablesmetadatahash as well as packageid. It does appear in the
$ndo$navappuninstalledapp as unpublished.
For whatever reason, it appears the unpublish was not properly recorded. Does anyone know of a way to get past this? Failing any good advice I am going to test modifying the $ndo$navappschematracking record and make it appear similar to the other unpublished extensions.
Help!
Regards - Noeline
We have a client on BC 21 - 2022 release wave 2 on prem, with a UAT database and a Production database. Recently we created a new instance and forgot to disable designer, and a user added a field to a page in designer. When we noticed it, we uninstalled, unpublished, and disabled designer. We now have a situation where we want to import a new company from the UAT to Production, and that extension is causing an error. It is not listed under extensions, nor under Get-NAVAppInfo.
After much research which yielded few results I scratched around in SQL and found the extension in $ndo$navappschematracking. Unlike the other extension which have been unpublished, that one still has a value in appstructuredtablesmetadatahash as well as packageid. It does appear in the
$ndo$navappuninstalledapp as unpublished.
For whatever reason, it appears the unpublish was not properly recorded. Does anyone know of a way to get past this? Failing any good advice I am going to test modifying the $ndo$navappschematracking record and make it appear similar to the other unpublished extensions.
Help!
Regards - Noeline
0
Best Answer
-
Options
ShaiHulud
Member Posts: 228
Have you tried Sync-NavApp for the orphaned extension with "-Mode Clean"? That one works on unpublished extensions and should cleanup any leftovers.
Failing that, I had luck in the past forcibly removing the entries from navappuninstalledapp table through SQL when it was not possible to run the Sync-NavApp which allowed importing of companies0
Answers
Failing that, I had luck in the past forcibly removing the entries from navappuninstalledapp table through SQL when it was not possible to run the Sync-NavApp which allowed importing of companies
Thank you for the tip. I did not try the -Mode Clean, but will try it tonight.