• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Duplicate Points - Over Mango Publisher Sync

    User help
    2
    8
    2.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mihairosu
      last edited by

      I know this is my fault, so I will explain how it got there, and am wondering how to fix this.

      So we have the two Mango servers (a MangoES and a Mango Main Historian)

      I created the points in MangoES and put them in the correct folder hierarchy. This is then synced to the Main Historian via persistent TCP.

      Here's where I made a mistake. I arranged most of the points (through the folder hirearchy tool) in the Main Historian BEFORE I synced the points, so now there are two instances of the points.

      What do I need to do to resolve this?

      0_1473430253821_duplicates.png

      1 Reply Last reply Reply Quote 0
      • phildunlapP
        phildunlap
        last edited by

        Hi Mihai,

        I wouldn't expect this to be related to the point hierarchy. I would guess you changed the xid prefix in the publisher, or created the receiving points some other way than letting the publisher create them?

        Can we see XIDs from two points that are the same? Maybe the JSON for those two points, too? There is probably a SQL command to delete the points if we can identify how / why their XIDs are different for the publisher.

        1 Reply Last reply Reply Quote 0
        • M
          mihairosu
          last edited by

          Here's the exported config file from the Main Historian. I deleted references to all other points in the one named Trimmed. However I do not see duplicate entries for the points.

          I didn't think I would need to export from the MangoES, because there everything is fine.

          Just in case I accidentally deleted the duplicates, though I don't think so, I've also included the Full config file.

          1_1473431553929_SP Export Trimmed.txt 0_1473431553928_SP Export Full.txt

          1 Reply Last reply Reply Quote 0
          • phildunlapP
            phildunlap
            last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • phildunlapP
              phildunlap
              last edited by

              I do not see the duplicates in either of those files. Can you verify that the duplicates exist on the data point details page? If so, what are the XIDs for a pair of duplicates? If not, can you save your hierarchy, clear your cache, and reload the hierarchy page?

              1 Reply Last reply Reply Quote 0
              • M
                mihairosu
                last edited by

                The Data Points DO exist as duplicates in the Points Details page.

                0_1473432868423_duplicates details page.png

                Aha! The duplicate and original XIDs differ because of a capitalized letter. I remember I tried to change the names of the points, though I don't exactly remember where I did it. I think it may have been on the MangoES, where they originate.

                Sorry I didn't put these in the first reply:

                0_1473433108284_XIDs.png

                1 Reply Last reply Reply Quote 0
                • M
                  mihairosu
                  last edited by

                  I was able to successfully delete the data points that were duplicates without any issues.

                  1 Reply Last reply Reply Quote 0
                  • phildunlapP
                    phildunlap
                    last edited by

                    Thanks for sharing the resolution!

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post