• 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

    SQL Data Source Statement Test

    Mango feedback
    2
    2
    622
    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.
    • BGB
      BG
      last edited by

      Hello,
      I am using Mango Core: 3.6.3, Mango API: 3.6.1, Mango UI: 3.6.3. I have not run the latest update.

      While working on my SQL data sources, I used the statement test as I usually do. But this is the first time I was working on the SQL data sources with the new UI.

      The statement had a spelling error for the selected table and could not find the table. The new UI did not tell me there was a problem. It just did nothing. I did not get a successful list of parameters below the statement obviously. I checked the MA.log and there was nothing in there either.

      I had to go back to the legacy UI and run the statement test there to get an indication of what the fault was. The legacy UI told me right away that it could not find the table, due to my spelling error.

      Is it possible to get these error messages displayed for the statement test on the new UI?

      Cheers

      Brian

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

        Hi Brian,

        Thanks for bringing this to our attention, I have created a git issue about it.

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