Jump to content
  • To Search the Seeq Knowledgebase:

    button_seeq-knowledgebase.png.ec0acc75c6f5b14c9e2e09a6e4fc8d12.png.4643472239090d47c54cbcd358bd485f.png

Search the Community

Showing results for tags 'powerbi'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Technical Forums
    • Tips & Tricks
    • General Seeq Discussions
    • Seeq Data Lab
    • Seeq Developer Club
    • Seeq Admin Forum
    • Feature Requests

Categories

  • Seeq FAQs
  • Online Manual
    • General Information

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Company


Title


Level of Seeq User

Found 3 results

  1. I am trying to export some data directly from Seeq to Power Bi using OData feed. In Power BI, I am missing some data which I am able to see when I export to Excel. In Excel, there is a "grid" tab that contains the relevant data I need in Power BI but this data (in grid) doesn't show up in Power BI. Am I doing something wrong?
  2. Currently in Seeq (June 2021) there is not a method to export ungridded signal data. There are a couple of development items in the works which will help in the future but for the moment this is the best work around for oData connections. As a reminder if you just need the data in excel, there is an ungridded raw timestamp option available for the excel export. Lets use the following setup as our example. We have a condition which represents my batches and we have a simple temperature signal that I want to get the average value of for each batch. Step 1 - Create my Average temperature per batch KPI using the Signal from Condition tool. In this example we are selecting the start of the batch to place the KPI timestamp. Step 2 - Re-grid my discrete points onto a known fixed grid. This step will loose some fidelity with the batch start timestamps and is the main drawback of this method. Pick a re-grid interval that ensures that you will not have two points inside the same interval (hours, minutes, days, weeks) $AveCycleTemp.aggregate(average(), hours(), startkey()) Step 3 - Step export on the same new grid by selecting Custom grid period and Days, minutes, hours to match your re-grid interval from Step 2. Select the OData Sample Table endpoint when you create the export. Step 4 - One final optional step to clean things up in your BI tool is to remove all the null points when you import the oData feed. The example below shows the process in the PowerBI Power query editor but there should be similar steps in other tools.
  3. For particularly large oData exports it can sometime be helpful to increase the default PowerBI timeout period. This is easily done in the advanced editor of the Power Query Editor. 1) To access the Power Query editor click the options menu on your table and select Edit Query 2) In Power Query select the Advanced Editor option to edit the advanced query parameters 3) in the OData.Feed() function add the optional Timeout parameter. The example below is for a 90 minute timeout Source = OData.Feed("https://explore.seeq.com:443/odata.svc/Export_67ExampleDataSignals_DataSet", null, [Implementation="2.0",Timeout=#duration(0, 0, 90, 0)])
×
×
  • Create New...