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

  • Hello All!

    We faced with error 1 while configuration import.

    Steps we have done is shown below.

    1. Open Configuration import/export page
    2. Select Event Handlers
    3. Click Export
    4. Click Import, without any change
    5. Then, Error 1 is seen on the screen.

    When we check the event handler, which gives an error, in the event handlers import JSON file, we see that some detectorsXID and dataPointXID is null shown like below.

    For Situation 1 , we have defined an event detector to the point "DP_74d73b67-41d1-49c1-a0fc-1b29d6921bb3" and selected the event handler for this event detector. After that, we directly deleted the event detector. Although we deleted the event detector, the point is seen as below in the event handler JSON export.

    For Situation2, we deleted point which has an event detector that we selected an event handler. Although we deleted point, the point is seen as below in the event handler JSON export.

    We solved the problem by deleting objects with null properties. How we can prevent from this problem, not to have the problem again?

    //Situation 1
            {
              "sourceType": "DATA_POINT",
              "dataPointXID": "DP_74d73b67-41d1-49c1-a0fc-1b29d6921bb3",
              "detectorXID": null
            },
    //Situation 2
            {
              "sourceType": "DATA_POINT",
              "dataPointXID": null,
              "detectorXID": null
            },
    

    Error 1:
    Event handler 'EH_086295d6-da94-4714-b350-3104832ca77e': saved
    Event handler 'EH_20bb44aa-cc63-417d-9781-92934af4b6ff': saved
    Event handler 'EH_d290da12-b346-4d0f-99fc-9dbfa160ab7a': Event type must have a 'detectorXID'
    Event handler 'EH_8ca1bc17-18b9-4ec1-a92e-0f94c9f35a7b': Event type must have a 'detectorXID'
    Event handler 'EH_33742af8-5d69-435f-8d2d-1493e91aa2dd': Event type must have a 'dataPointXID'
    Event handler 'EH_f0ff4774-bc57-4612-b3e5-b6fdaf151fa9': Event type must have a 'detectorXID'
    Event handler 'EH_1fb091b1-ea9a-4092-8172-799f677676e0': Event type must have a 'detectorXID'
    Event handler 'EH_a89c16f2-336a-438e-a8dd-58ca2fefd86d': Event type must have a 'dataPointXID'

    Thanks a lot!


  • @Nurr I just tested this on the latest development branch of Mango and this is fixed. So this will be fixed in the Mango 4.0 release. You didn't specify the version of Mango or how you did the deletes (legacy UI, new UI, REST call from custom page etc.) so I only tested it from the new UI in our development branch but in Mango 4.0 there is only 1 place this can happen now so I am confident it is fixed.


  • @terrypacker Mango core version is 3.7.5 and I have tested on new UI. We are looking forward to seeing Mango 4.0 release, when it will be available for us?

    Thanks!