• Moving a Maildatabase

    By Max Satt 1 decade ago

    Hi there!



    I'am earching for a solution to transfer mails, calendar entries, … from a template 8.5 mail-db to an 6.0.3 mail-db.

    I thought Data Moving Animal is the tool i'am searching for, but there is a problem.

    Unfurtunatly there is no primarykey to search for to make the "action if target document found using key" working correctly.



    Is there any possibility to realize it?

    • Key is optional

      By David Jeyachandran 1 decade ago

      Hi Max,



      The key and the search view are optional. If you want to simply transfer (copy) documents you do not need a key. The key is only necessary if you want to update documents and the key is used to match the source document to the target document.



      If you want to copy all the documents in a database to another, it's simple. You have to select a form so just select the default form for both the source and target databases. On the second tab, select documents using a Selection formula and use "@All". You will need to put this in place of "Form="Memo"" which will automatically default. I think that the rest should be simple.



      Please let me know how this goes.



      Kind Regards

      David

      • By Max Satt 1 decade ago

        Hi David!



        I've tried what you suggested, but….



        On the first time the data move is working quite fine, all mails, calendar entries where copied in the target database. But if i repeat it, i'am getting duplicates of all records.

        Therefore i need a "primarykey" in both databases to update when a document is changed in the source db, or skip a document-copy when it is allready in the target database.



        Unfortunalty i cannot find a suitable key to match the documents in both databases.

        I'am also give a try to use the "@DocumentUniqueID", but first, it's not possible to select it as a key, because it is not a field of the document, only a property.

        And second, the UNID in the target-document is of course not the same.



        I went a step further and created a field in the target db, called myDocumentUniqueID, which i wanted to fill with the sourcedocument-UNID to match against the source-DB.This experiment does not even work, because it is only possible to compute values from the targed-DB.



        Any other suggestions?



        Kind regards

        Markus










        • This is a tough one

          By David Jeyachandran 1 decade ago

          Hi Markus,



          It sounds like you have thought about every option I could think of. I can see the problem of finding a primary key to link documents between databases. I am currently working on a new release of the Data Moving Animal that will allow you to set fields on the Target document based on formulas run on the Source document. This will make it easy to write Source document UNID to the target document. I have not got a release date for this since I am just doing this in my spare time. I'm guessing that this should be completed in November.



          In the meanwhile try this….

          Write a scheduled agent that writes the Source docID to a field (SourceUNID) to all new documents in the Source database. Include this field in the list of fields to copy to the target database. Create a view in the target database based on SourceUNID. This should then allow you to match based on the SourceUNID. This is a little complicated but I think it is possible to make this work.



          Let me know your thoughts.



          Regards

          David

          • Running formulas on the Source Database

            By David Jeyachandran 1 decade ago

            Hi Markus,



            On the 17th November I will release the next version of the Data Moving Animal. This will enable you to write the Source document UNID to the target document. In fact you can run any formula on the Source document and write this to the Target document.



            This is a long-awaited feature! Currently you can only run formulas on the Target document.



            Thank you to those who have assisted in testing the beta.



            Regards

            David