Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Gambit 20 posts 100 karma points
    Feb 07, 2017 @ 13:34

    Strange behavior during definition export via SQL script

    Hello. I'm using CMSImport PRO 3.6 and tried to export import definition to another DB (from stage to Prod environment). The steps are simple:

    1. Create definition manually, configuring login/password/mapping/e.t.c.
    2. In CMSImportState find the record, and create "Insert" script by copy necessary data. enter image description here
    3. I have execute "insert" script on another DB, and after that I'm able to see them in "Content" folder.
    4. I select "SocialEye NL", one of the imported definition, to change "Location". However, another definition is selected. enter image description here
    5. However configuration belongs to the definition which I clicked on. When I reach the step when I can save the changes, I receive the name of "selected" definition. enter image description here
    6. If I change it to "SocialEye NL", the name will be changed for "SocialEye FR" definition. In result, we receive the following result: enter image description here

    Summary: This happens most of the time, when we insert "Definition" into "CMSImportState" table.

  • Richard Soeteman 4039 posts 12887 karma points MVP 2x
    Feb 08, 2017 @ 09:04
    Richard Soeteman

    Hi maybe it's because a key already exists, but export import of definitions is on the list of things to implement.

    When doing this make sure the document type structure and all db iud's are exactly the same otherwise things can go wrong.



  • Gambit 20 posts 100 karma points
    Feb 08, 2017 @ 13:00

    Hello Richard,

    By "Key", do you mean "UniqueIdentifier", or maybe another field in another Table? Because, as you can see from the screenshot above, all key values are unique.

    And what do you mean by "document type structure"?

    I create "insert" script from one DB, and execute it on another with empty "CMSImportState" table, but receive the same behavior.

    Any thoughts?

    Thank you

  • Richard Soeteman 4039 posts 12887 karma points MVP 2x
    Feb 08, 2017 @ 13:02
    Richard Soeteman

    What you are doing is unsupported so if id's don't match it could conflict. Can think of many things that could go wrong.

  • Gambit 20 posts 100 karma points
    Feb 09, 2017 @ 17:04

    Hi Richard,

    You were right! Somehow, I have misplaced Id's. Moreover, I have done it a couple of times.

    I have noticed it only after I serialized the ImportState, and check the StateIdentifier: enter image description here

    Sorry for misunderstanding, and thank you for help!


Please Sign in or register to post replies

Write your reply to: