Menu

BUG? Synchronization Data Sources -> Field "Reconciliation policy: Use the attributes" without effect

2019-09-06
2019-09-10
  • Philipp Sponsel (evosoft)

    Hi Folks,

    i guess i found a bug.

    Configuration:

    TheReconciliation policy: Use the attributes seems not to have any effect it is still mapping against the primary_key which is very bad for me as i'm generating my csv before every run an the primary_key is never allocated to the same employee_number.

    I'm Using iTop-2.6.1-4463 | Ubuntu | MariaDB

    Has anyone else had this issue and found a workarround or solution? Or am i just to stupid to do the right configuration?

    Best Wishes,
    Philipp

     

    Last edit: Philipp Sponsel (evosoft) 2019-09-06
  • Jeffrey Bostoen

    Jeffrey Bostoen - 2019-09-06

    Could you show us a (censored) version of the datatable?

     
  • Philipp Sponsel (evosoft)

    Hi Jeffrey,

    sure! i've just started a fresh installation i'll come back to you tomorrow

     
    👍
    1
  • Pierre Goiffon

    Pierre Goiffon - 2019-09-10

    Hello,
    There were some problems with deletion policy in 2.6.0 and 2.6.1... That was fixed in 2.6.2 but there was no package generated for the community (the tag exists in the repo though)
    Is this your problem ?

     
    • Philipp Sponsel (evosoft)

      Hi Pierre and thanks for your reply!

      Maybe it is my problem just have a loop at the very recent post i've made. there you'll find more informations. meanwhile i'll try ti update to 2.6.2 and report back if this solves my problems.

       
      • Philipp Sponsel (evosoft)

        Hi Pierre,

        IT WORKS NOW! Thanks! :-) installing 2.6.2 did the trickt :-)

         
        👍
        1

        Last edit: Philipp Sponsel (evosoft) 2019-09-10
    • Philipp Sponsel (evosoft)

       

      Last edit: Philipp Sponsel (evosoft) 2019-09-10
  • Philipp Sponsel (evosoft)

    Hi Jeffrey,
    okay the issue is back.

    I've got some screenshots for you:
    Here are the Synchro Data Source Settings:

    As you can see: i'm trying to map against Attributes (Employee Number)

    Now lets have a look at the Synchro Replica Report:

    it is doing it again! it maps against the primary_key and not against the employee number :-( I dont get why it is doing this.

    You also asked for a screenshot of the table itselfe:

    I realy hope that you can help. i'm evaluating this product right now and this would be a total bock which would cause me to look for somehting else.

    Any ideas/tips/tricks or advices you've got for me?

     

Log in to post a comment.

MongoDB Logo MongoDB