Cleanest way to uninstall customized forms or code

slentz
Member Posts: 14
Is there an "uninstall" routine or something I can use to remove customizations from my Navision?
Thanks!
Thanks!
0
Comments
-
no uninstall.
If you have a backup of the objects before the change was made you can import the old object.
What's the problem with the changes?0 -
Savatage wrote:no uninstall.
If you have a backup of the objects before the change was made you can import the old object.
What's the problem with the changes?
Nothing that I know of. Just thought if the situation ever came up where a customer of mine may want to remove the customization for whatever reason.0 -
I would think all customizations are tested first with the customer before implimenting it into the Live Database.
If he say's Ok then I guess you can charge him to remove it later down the road 8)0 -
-
The step back is possible only if there are no data in new fields etc. If the new fields are filled up, you need to clear them... and of course, there is possibility that the data can be inconsistent after that step...0
-
What if you get your Cronus objects, import them, and on the worksheet, select replace all.
i think you will be as clean as CRONUS!$cside -MBS
>install Navision::4.0 SP1
>q
$
oOo0 -
That only works if you don't have any data in fields that were added. Otherwise the object import will just fail.0
-
Hi!
Whenever I do a release, I do my development in a local copy, export the objects from the local copy, export and archive the previous version of the objects from our server master copy of the client's system, install my changes and then send them on to the client (After testing).
If the client installs the changes on the lives system and then for whatever reason wishes to revoke the changes, I can send them the *.fob file with the previous set of objects (and turn back the master server copy as well).
As Daniel pointed out, if there have been field changes, then it is usually necessary to write an "upgrade" routine to reformat the data first.
This procedure is also useful in the event that a client claims that your release has changed something you know it definitely has not.
Experience has taught me that this works very well however, I do not remember the last time I had do do such a "roll back"!Edward Bloomfield
Lead Consultant
Theta0
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