Analyze FOB files before importing them...

jemmy

Folks/Navision gurus,

Usually we analyze fob file after we did import command from Navision, if there's a conflict then Navision would open Worksheet and ask us how the action should be done? Well, I really can't imagine what objects are actually inside the fob files.
Sometimes they mentioned Replace, New, Merge., etc.

My question is how can we determine all of these, for example I got a terrible importing (can't get success with all selected actions). Then I think we need to analyze FOB files before importing them, how to accomplish this? :roll:

Developer Toolkit is good, but it only works for text files (let me know if I go to wrong direction on this).

That's all about it, your advices should be appreciated.


Jemmy

kine

If you are customer, your NSC send you prepared fob and you import it with "replace all"... If you are NSC, you must know, what you have in your DB and what are you trying to import - because you know from where it comes. It is some fob exported from some DB - you have the object in this db...

If you don't know, what are you importing, you must import it into some clean DB (Cronus) and look at the objects. After that you can "merge" the objects into your database...

jemmy

Hi Kine,
Thank you, I really appreciate your share thoughts...
That's what I do as usual. now I'm sure that I don't go to wrong direction on this.
Anyways, I would suspect a tool that can convert .fob to .txt? haha..
If this is the best way to accomplish this, I'll be rigid doing it next time. Sometimes, I really dislike troublesome things... so lazy

kine

There is no way to decode fob into txt... it is same as decode binary data of objects from BLOB field in Object table... No possible becose coding... only text header in fob can be read...