Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
The R script component should be able to extract all objects of the class data.frame, produced by an R script.
If I simply produce standard data.frame objects, it will indeed pick them all up. If however, I use one of the common packages that enhance data.frame objects like data.table or dplyr, I start getting unstable behaviour.
Basic data.frames:
iris1<-iris iris2<-iris
Using data.table:
library(data.table) iris1<-iris # shows up iris2<-iris # shows up iris3<-setDT(copy(iris)) # shows up iris4<-setDT(copy(iris)) # doesn't show up
Using dplyr:
library(dplyr) iris1<-iris # shows up iris2<-iris # shows up iris3<-tbl_df(iris) # doesn't show up iris4<-tbl_df(iris) # doesn't show up
Such behaviour could be related to how PowerBI interrogates the class of the objects in the R workspace. Ideally, it should see if objects `inherits()` data.frame and extract those that do
PowerBI desktop: Version: 2.32.4307.641 64-bit (February 2016)
R: 3.2.4
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 5 | |
| 5 | |
| 4 |