Thorsten Vogt Posted February 20, 2020 Share Posted February 20, 2020 Hi, I came across this issue when I used Seeq Data Labs for uploading data from an Excel file into Seeq. The file contained some signals, that used "1/Min" as UOM. While uploading the data to Seeq I got the message that the Unit is not supported. I created a sample with one signal to reproduce the issue: Is there a way to let SDL check for invalid units before pushing data back to Seeq? The bad thing is that the signal is created in Seeq and cannot be archived within SDL or Seeq Workbench: Only way to archive these items seems to be using SDK or REST API. Regards, Thorsten Link to comment Share on other sites More sharing options...
Seeq Team Mark Derbecker Posted February 20, 2020 Seeq Team Share Posted February 20, 2020 Hi Thorsten, In an upcoming version of Seeq Server (R22.0.46.xx) it will be possible for SPy to verify units prior to pushing. (We needed to fix a problem in the REST API that was preventing SPy from querying Seeq Server for the list of supported units.) I'll circle back to this thread to notify when SPy has the capability, but keep in mind that you will need to upgrade Seeq Server as well. Mark 1 1 Link to comment Share on other sites More sharing options...
Seeq Team Mark Derbecker Posted February 20, 2020 Seeq Team Share Posted February 20, 2020 With respect to archiving, I think if you change `Archived` to `True` in the DataFrame and then `spy.push()` that item, it should mark it as Archived. Have you tried that? Note that the `spy.push(archive)` argument is a little misleading-- it is used for another purpose. I'll think about whether to rename that for clarity. Link to comment Share on other sites More sharing options...
Thorsten Vogt Posted February 20, 2020 Author Share Posted February 20, 2020 22 minutes ago, Mark Derbecker said: With respect to archiving, I think if you change `Archived` to `True` in the DataFrame and then `spy.push()` that item, it should mark it as Archived. Have you tried that? Note that the `spy.push(archive)` argument is a little misleading-- it is used for another purpose. I'll think about whether to rename that for clarity. Hello Mark, like this way? The body of "Push Result" is: '{"statusMessage":"Invalid unit \\u0027/Min\\u0027"}' Regards, Thorsten Link to comment Share on other sites More sharing options...
Seeq Team Mark Derbecker Posted February 20, 2020 Seeq Team Share Posted February 20, 2020 Ahhh, yes I see. That won't work because it's rejecting the overall POST. I'll think about how to possibly fix. Link to comment Share on other sites More sharing options...
Seeq Team Mark Derbecker Posted March 4, 2020 Seeq Team Share Posted March 4, 2020 Thorsten, I tracked this down to a non-obvious issue with your initial push wherein you specified `Value Unit of Measure` instead of `Value Unit Of Measure`. (Notice the case difference on the word "of".) Unfortunately due to another issue with Seeq Server, once you push with the wrong case, the signal becomes "tainted" and you can't make any changes to it via a normal spy.push. As you found, you can only archive it with the SDK. I'm going to add appropriate guards and error messages to spy.push() that prevent inadvertent use of the wrong case, and I'll also log a bug report in our system to fix Seeq Server. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now