Duplicate Points - Over Mango Publisher Sync
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?
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.
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.
This post is deleted!
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?
The Data Points DO exist as duplicates in the Points Details page.
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:
I was able to successfully delete the data points that were duplicates without any issues.
Thanks for sharing the resolution!