R.Execute example without the use of R.Execute() in Power Query [behind the scenes this gets executed bin\x64\Rscript.exe" --encoding=UTF-8 RScriptWrapper.R"]

100%

R.Execute example without the use of R.Execute() in Power Query [behind the scenes this gets executed bin\x64\Rscript.exe" --encoding=UTF-8 RScriptWrapper.R"]

✓ Published0🌍 Public

Last edited Aug 21, 2017

Created on Aug 14, 2017

This example demonstrates how to execute an R script from within Power Query without explicitly invoking the `R.Execute` function, instead relying on the `AdoDotNet.DataSource` with the `R.Provider` to run a native query. The code passes a string containing an `output` variable that captures the result of `system2("whoami", stdout=TRUE)`, which retrieves the current username. The resulting table is then converted from binary R data using `RData.FromBinary`. This approach showcases the underlying use of `Rscript.exe` via the provider, highlighting an alternative integration path for R workflows in Power Query.

AI-generated description

Similar vizzes

Loading thumbnail…

STDOUT as data source in Power Query M

This example demonstrates how to capture a command-line program's standard output as a data source in Power Query M. It shows a minimal query that retrieves the current user name by running the `whoami` command, then feeds that result into a table. The implementation relies on the `R.Execute` function to invoke an R script, which uses `system2` with `stdout=TRUE` to capture the command's output, and `read.table` to parse it into a data frame. The resulting table is then returned as the query's output. This approach highlights a practical bridge between operating system commands and Power BI's data transformation layer.

HHugoberry

74% match

Loading thumbnail…

Using R.Execute() in Power Query to export the contents of a table to CSV

This example demonstrates how to use R.Execute() in Power Query to export a table’s contents to a CSV file. The code generates a seed list of numbers from 1 to 1,000,000, converts it into a table, and then passes that dataset to R’s write.csv() function via the R.Execute() API. The R script writes the data to a specified file path. The visualization highlights the integration between Power Query and R, showing how R’s data-export capabilities can be invoked directly within a query pipeline, without additional manual steps.

HHugoberry

72% match

Loading thumbnail…

Power Query script to get msmdsrv.exe port number via R

This example shows how to retrieve the port number of the msmdsrv.exe process by combining R scripts with Power Query’s M language. It first runs a system command via `system2` to capture the task list and netstat output, then parses the results using `read.fwf` with fixed-width columns. The M code invokes the R script through `R.Execute`, formats the resulting tables with `Table.TransformColumns` and `Table.PromoteHeaders`, and finally joins the process ID from the task list with the matching netstat entry to extract the local address port. The visualization relies on text-based data processing rather than graphical libraries.

HHugoberry

69% match

Loading thumbnail…

Writing 10M lines of a query result to a table in Power Query via R

This example demonstrates how to write 10 million rows of a query result to a CSV file from Power Query by invoking an R script. It shows the integration of Power Query’s table generation with R’s file-export capabilities, specifically using the `R.Execute` function to run `write.csv` on a dataset. The Power Query code creates a list of numbers from 1 to 10,000,000 via `{1..10000000}`, converts it to a table with `Table.FromList`, and passes that table as the `dataset` parameter to the R script. The R script then writes the data to `d:\Downloads\out.csv`.

HHugoberry

69% match

Loading thumbnail…

Exporting data out of Power Query via AdoDb route

This example demonstrates how to export data out of Power Query by directly inserting rows into a SQL Server table through an ADO.NET connection. It uses the `Sql.Database` function to connect to a local server instance and the `Value.NativeQuery` API to execute a parameterized `INSERT` statement, passing literal values for the `@key` and `@value` parameters. The code shows a concrete way to push query results into an external database, bypassing Excel’s native output options. The visible data source is a SQL table named `[dbo].[Demo]`, and the approach highlights ADO.NET’s role in bridging Power Query transformations to persistent storage.

HHugoberry

67% match

Loading thumbnail…

Power Query CurrentUser via a lightweight PowerShell HTTP API

This example demonstrates how Power Query can obtain the current Windows user by querying a lightweight PowerShell HTTP API. It shows the result of a `whoami` command wrapped in a JSON response. The Power Query code uses `Web.Contents` to call the local HTTP endpoint at `http://localhost:8888/?command=whoami`, and then parses the returned JSON with `Json.Document`. The underlying HTTP API service is built from a PowerShell script, based on the referenced blog post, which executes commands and returns their output. This approach provides a simple bridge between Power Query’s data-fetching capabilities and PowerShell’s system introspection.

HHugoberry

66% match

Loading thumbnail…

Gist bae6758b4e3645b55f022e6432f29458

This visualization demonstrates the interaction between R and PowerShell, showing how a system call from an R environment triggers a PowerShell script that manipulates data. The code uses the `system2` function to execute a PowerShell command with a specified file path, passing arguments to run `coolScript.ps1`. The example highlights the practical integration of two scripting environments, where R serves as the orchestrator for external process execution. The rendering relies on the command-line interface rather than graphical libraries, focusing on the workflow of invoking and managing external scripts from within an R session. The data flow is implicit in the script's execution, emphasizing interoperability over visual output.

HHugoberry

66% match

Loading thumbnail…

Getting $Embedded$ connection details in Power Query via R

This example shows how to extract connection details for the Power Query engine by querying system processes and network ports. It retrieves the process ID of `msmdsrv.exe` from a filtered `tasklist` command and then cross-references it with TCP port information obtained via `netstat`. The R script parses the command-line output into fixed-width tables using base R functions (`read.fwf`, `textConnection`, `system2`). No external visualization libraries are used; the focus is on data wrangling through R's base I/O and text-processing capabilities, making the connection details available for later analysis.

HHugoberry

65% match