RWS Community
RWS Community
  • Site

Trados Studio

Trados Team

Trados Accelerate

Trados Enterprise

Trados GroupShare

Passolo

MultiTerm

RWS AppStore

Connectors

Beta Groups

Managed Translation

MultiTrans

TMS

Trados Enterprise

WorldServer

Language Weaver

Language Weaver Edge

Language Weaver Connectors

Language Weaver in Trados Studio

 

 

Content Champions

Tridion Docs

Tridion Sites

Contenta

LiveContent

XPP

Trados Studio Ideas

Trados GroupShare Ideas

Trados Team Ideas

Trados Team Terminology Ideas

Trados Enterprise & Accelerate Ideas

MultiTerm Ideas

Passolo Ideas

RWS Appstore Ideas

Tridion Docs Ideas

Tridion Sites Ideas

Language Weaver Ideas

Language Weaver Edge Ideas

Managed Translation - Enterprise Ideas

TMS Ideas

WorldServer Ideas

Trados Enterprise Ideas

XPP Ideas

GroupShare Developers

Language Cloud Developers

MultiTerm Developers

Passolo Developers

Trados Studio Developers

Managed Translation Developers

TMS Developers

WorldServer Developers

Tridion Docs Developers

XPP Developers

Language Combinations by Language Services

RWS Training & Certification

Style Guides

LDE Korean Vendor Support

RWS Campus

Trados Approved Trainers

Nordic Tridion Docs User Group

Tridion West Coast User Group

Community Ops

RWS Community Internal Group

AURORA

Internal Trados Ideas

Linguistic Validation

Mercury

QA Tools

RI Operational Excellence

Trados Inspired

XPP Cloud

Recognition & Reward System

RWS Community Platform Related Questions

Community Solutions Hub (Trados)

About RWS

Events

RWS Services: Train AI & others

RWS Training & Certification

To RWS Support

  • Search
  • Translate

    Detecting language please wait for.......


    Powered by
  • User
  • Site
  • Search
  • User
  • Products
  • Language Weaver Solutions
  • Language Weaver Edge
  • More
  • Cancel
Language Weaver Edge
  • Products
  • Language Weaver Solutions
  • Language Weaver Edge
  • More
  • Cancel

Language Weaver Edge > Wiki

Connecting Power BI to Language Weaver Edge
  • Home
  • Blogs
  • Leaderboard
  • Forum
  • Videos
  • Wiki
  • Docs
  • More
  • Cancel
  • New
Show Translation Options

Detecting language please wait for.......


Powered by
Language Weaver Edge requires membership for participation - click to join
  • Wiki
  • Supported Language Pairs and Versions for Language Weaver Edge
  • Language Weaver Edge: Deployment types and features availability
  • Out-of-the-box connectors available for Language Weaver Edge customers
  • Adaptation of Language Pairs in Kubernetes GPU Nodes
  • Associating User Feedback to a New Language Pair (Generic, Adaptable or AutoAdaptive)
  • Connecting Power BI to Language Weaver Edge
  • End dates for CentOS Linux 7 and CentOS Stream 8
  • Running Language Weaver Edge on Docker
  • Running Language Weaver Edge on Kubernetes
  • Edge Release Versions

Connecting Power BI to Language Weaver Edge

You can follow the steps below to connect Power BI to Language Weaver Edge.

Full details on the Language Weaver API can be found in the Edge API documentation.

1. Getting the connection details

You will need to have at hand the following information in order to establish the connection with Language Weaver Edge.

  • <API Base URL>: This is the URL that will be used to connect to the Language Weaver Edge API. To find out the API server host and port, log into the Language Weaver Edge Web GUI as an admin user and click on [Username] > My Account.
    The URL will be something like https://languageweaveredge-url.com:8001/api/v2.



  • <API Key>: This is a credential equivalent to a user and password that allows you to access Language Weaver Edge via the API. To find out the API Key, log into the Language Weaver Edge Web GUI as an admin user and click to [Username] > My Account.
    The API Key will be something like u_user@example.com_NM2ba8j9pHQ2.



2. Creating the tables in Power BI

Follow the steps below to create a table in Power BI for each query with all the historical data.

  1. From Power BI, click con Home > Get data > Web.



  2. In the From Web window, add any of the following queries depending on what you need to report.



    Report Type Query
    Cumulative translation totals <API Base URL>/reports/totals/translations
    Cumulative translation totals per language pairs <API Base URL>/reports/totals/translations/language-pairs
    Cumulative translation totals per users <API Base URL>/reports/totals/translations/users
    Detailed report of translations <API Base URL>/reports/translations

    Important: You need to replace <API Base URL> with your actual Edge URL.

  3. Click on OK. The Access Web content window will show up.
  4. Go to the Basic tab and enter your <API Key> under the User name field. Leave the Password field empty.



  5. Click on Connect. A new table will be created with the results of the query. You can remove or reorder columns as needed.
  6. Repeat the previous steps for each of the reporting queries you wish to run.

3. Adjusting the queries to a specific time frame

You can also adjust a query to a specific time frame. In this way, if you need to report on a monthly basis, for example, you can run a query per month, add a new date column to each table and then merge them in a single one.

To adjust a query to a specific time frame, follow the previous steps adding the following parameters to the queries:

Parameter Description Example
fromTimestamp The “from” date in the format yyyy-MM-dd <API Base URL>/reports/totals/translations/language-pairs?fromTimestamp=yyyy-MM-dd
toTimestamp The “to” date in the format yyyy-MM-dd <API Base URL>/api/v2/reports/totals/translations/users?toTimestamp=yyyy-MM-dd
fromTimestamp & toTimestamp Using both fromTimestamp and toTimestamp <API Base URL>/reports/totals/translations/language-pairs?fromTimestamp=yyyy-MM-dd&toTimestamp=yyyy-MM-dd


Examples:

Report Type Period Query
Cumulative translation totals From January 2022 to date <API Base URL>/reports/totals/translations?fromTimestamp=2022-01-01
Cumulative translation totals per language pairs Historical up to December 2021 <API Base URL>/reports/totals/translations/language-pairs?toTimestamp=2021-12-31
Cumulative translation totals per users March 2022 <API Base URL>/reports/totals/translations/users?fromTimestamp=2022-03-01&toTimestamp=2022-03-31
Cumulative translation totals January, February and March 2022 <API Base URL>/reports/totals/translations?fromTimestamp=2022-01-01&toTimestamp=2022-03-31

4. Getting all the records from the detailed report

When running the “Detailed report of translations” query (<API Base URL>/reports/translations), only the first 25 records will be shown. The last column in the resulting table, named “totalItems”, indicates the total number of records in the database.

In order to get all the records from the database, you will need to use the “perPage” parameter and set it to the value of “totalItems”.

So, for example, if when you run

<API Base URL>/reports/translations

the value for totalItems = 1500, you will need to run the following query to get all the records:

<API Base URL>/reports/translations?perPage=1500

  • Share
  • History
  • More
  • Cancel
Related
Recommended
  • Our Terms of Use
  • Copyright
  • Privacy
  • Security
  • Anti-slavery Statement
  • Cookie Notice
  • YouTube