Coming Soon: Exporting and Importing Companies and Other Data

Coming Soon: Exporting and Importing Companies and Other Data

Rate This
  • Comments 11

We are not quite ready yet, but we will soon announce the availability of new functionality for Microsoft Dynamics NAV 2013 R2: The ability to export business data, global data, and/or applications from one database and import the data into another database. Many of you used the FBK functionality to do this in earlier versions of Microsoft Dynamics NAV, but since we removed that backup/restore functionality in Microsoft Dynamics NAV 2013 R2, you have let us know how much you relied on it in your daily work. So we are working hard on this new functionality, and we will make an announcement when you can download the update.

When the update is available, we will also update the Microsoft Dynamics NAV 2013 R2 Release Notes Follow-Up document, which is available here: https://mbs.microsoft.com/downloads/customer/NAV/NAV%202013%20R2/MicrosoftDynamicsNAV2013R2_ReleaseNotesFollowup.pdf

Best regards,

The Dynamics NAV team

Leave a Comment
  • Please add 3 and 2 and type the answer here:
  • Post
  • I understand that this is being worked on "hard", but was the development team so far removed from how this product is used on a daily basis that they were blindsided by the large number of requests for this functionality?  And I would hope this functionality is sitting on the back burner as the data loss hotfix is worked on...

  • Yeah well, usually I'm the one good for a rant, but that's potentially good news, I'll say. I'm curious on how this can be used, though. My preferred interface would be a (shock!) menu entry in the dev environment, and a CLI like powershell, too. So... fingers crossed :)

    with best regards

    Jens

  • Great news :)

    FBK was helpless if any table changes existed between the two databases. I hope this new functionality can handle that in other ways than aborting.

    (and please offer genuine replacement when removing essential functionality in the future)

  • Hope this works between different SQL Versions. Today, if my Customer has a different SQL version then the version I have on my machine, I cannot restore that backup. That was not a problem with FBK.

    In an effort to modernize (pun intended), Microsoft is ignoring some of the good old functionalities which were very useful in the Classic Version.

    Krupesh

  • What Krupesh mentioned above with regards to being able to import .fbk files into a different version of SQL is likely one of the most important features related to the old NAV backup and restore functionality.  Ideally this would not be a problem, but with all of the SQL versions that clients are one, it can be problematic to have the same version.  

  • I have been reading for months that this has been in the works, but is there some sort of deadline we can look forward to rather than the always ambiguous "soon"?  Have to say thanks to the team putting this together as it is a great convenience to the partner channel!

  • Are there any new information about the publication date of this urgently needed feature?

  • Yes, it's good news; but don't expect it soon; this is going to be one of those 'vapourware' things that MS are so good at.

    The problem is the dumb mistake that they made when the first RTC version was going to be V5 and it was taking "forever" to startup the RTC because the objects were being converted (called "processed" now) into C# and then the C# compiled all at run time.

    So to hide the time it took they split it in two and did the conversion to C# when the object was saved leaving the C#->DLL and the DLL->machine code compiles at run time. Still very slow but not quite as noticeable.

    It was a real WTF moment for me when I worked out how this worked! It was even worse when I realised that they never saved the DLL/object files!

    This basically makes it impossible for anything but the 'classic client' to import objects, save objects or load fbk files until they rewrite it. Even company data is impacted because, as it stands, a fake object gets created while the company data is loaded before it's merged.

    The fake object/merge technique is what makes the "load company data into a test database with different objects" possible. Even in the face of deleted columns, if you're prepared to recreate the column when the FBK throws the error (then resume the restore).

    Oh, and don't expect it to work with every version of Nav like FBK files used to. Because "Microsoft are never wrong".  Sigh.

    PS: We might get something sooner if it's allowed to throw away data.

  • Any update on this functionality?  I've been reading for months that this is being worked on and all we get is an announcement without and level of detail, a brief description of what functionality is actually being worked on would be comforting...

  • "Coming soon"?

    Please stop all work on the Rocket powered multi-tenant table juggling machine, and provide partners with the essential tools you've just removed

  • in wich versión of nav 2013r2 can restore a db simple, i have a lot of trouble with this funcionally. i cant restore using powershell. thanks

Page 1 of 1 (11 items)