Cleanest way to uninstall customized forms or code

slentz

Is there an "uninstall" routine or something I can use to remove customizations from my Navision?

Thanks!

Savatage

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?

slentz

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.

Savatage

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)

Savatage

kine

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...

admoretutsie

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!

DenSter

That only works if you don't have any data in fields that were added. Otherwise the object import will just fail.

Edward_Bloomfield

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"!