Jump to content

Power BI and SEEQ compatibility


Go to solution Solved by Sepideh R,

Recommended Posts

Posted

I understand that capsules and signals that have been created in SEEQ are saved in a data base and could be cached. Is it possible to read all these capsules in Power BI?

  • Solution
Posted (edited)

Thanks for reaching out. The short answer is yes and you can find more information about that in our KB page here:

https://seeq12.atlassian.net/wiki/spaces/KB/pages/112868662/OData+Export

Please kindly note that the data is static so to refresh the dashboard or analysis you must re-export OData for the new time-period, trends, and calculations as desired. This issue is currently backlogged in our internal work item (   CRAB-8611 BACKLOG  ) and will be in our release early this year in which you will be notified accordingly.

Edited by Sepideh R
  • 3 months later...
Posted

Thx Lindsey--  are there any plans to go to the more recent versions 3.0 and 4.0?  Also, will the odata calls ever be supported in the Seeq API calls?  The Reports group only supports export to powerpoint.  Many thanks.:classic_smile:

 

Kevin

  • Seeq Team
Posted

We don't have any short-term plans, but I have logged that internally as CRAB-15636 for future consideration. If you have specific use cases or integration requirements, those would be helpful. Thanks!

  • Like 1
  • 1 year later...
Posted

Hi,

We use SEEQ in our company to do calculation for our data from PI Historian. I would like to transfer the calculated data into MS Power BI to be incorporated into various dashboards. I can see that I can export data from SEEQ to MS Power BI through OData export and I have tried that successfully. My question is that how to automate this export, so that the data is automatically sent to MS Power BI on certain period without the needs to someone to export it manually. 

Many thanks,

  • Seeq Team
Posted

Hi Leonardw,

You will see in the OData Export Knowledge Base article (https://support.seeq.com/space/KB/112868662/OData%20Export) that there is an option for an auto-updating OData feed. This feature requires a premium license so if you do not have that feature available, please contact your Seeq Sales Executive for more details on the premium license. If you are unsure of your Seeq Sales Executive, please private message me what company you work for and I can point you to the correct person.

  • 1 year later...
Posted

Hello,

I wanted to use the OData export feature to PowerBI feature but I am having issues to login.
We have single sign on in our company. I tried my windows login as well as the original login I had before we got single sign on set up; non worked.

Wondering if that is something someone can help me figure out or confirm if perhaps our IS team need to provide me some login credentials ?

Thanks in advance

image.png.624f8150430f27c81032c9eb12ef51b3.png

Posted

thanks. That seems to work.

I am running an issue where I have "duplicate" exports and that prevents me from loading the export all together. 
-> Is there a way to delete exports if i am NOT an admin?
-> Also, is Seeq creating an export duplicate if i try to "export ODATA" of a workbench twice let's say?

Capture1.PNG

  • Seeq Team
Posted

Kenny, 

There is not currently a way to delete oData exports for non-admins. However, the exports do not put any load on the Seeq system unless they are being used by an external system (PowerBI, Tableau, etc) 

To answer your second question we are creating a new export url endpoint every time someone runs the tool in workbench. These oData feeds are in active development and we have plans for making the creation and maintenance of them easier in upcoming releases. 

  • Thanks 1
  • 2 years later...
Posted

Hi everyone.

I got an issue while using OData Export to visualize my data on Power BI.

After using an access key, I got this error message:
image.png.7c4247dcd6709ecc4cd10955b3c23ccf.png

It says: 
Unable to Connect We encountered an error while attempting to connect. Details: "The feed metadata document does not appear to be valid. Error: A type has conflicting definitions for the property max"

What might I have done incorrectly ?
Thanks for your responses,

Adam

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...