<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: survey 123 and Power BI in ArcGIS for Power BI Questions</title>
    <link>https://community.esri.com/t5/arcgis-for-power-bi-questions/survey-123-and-power-bi/m-p/764060#M45</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Upvote this idea &lt;A _jive_internal="true" href="https://community.esri.com/ideas/13853-arcgis-data-connection-for-power-bi"&gt;https://community.esri.com/ideas/13853-arcgis-data-connection-for-power-bi&lt;/A&gt;. In that idea is a user comment that suggests a&amp;nbsp;workaround. If your form is simple enough (no repeats or attachments) and if you are good at JSON transformation using DAX and PQE, it should be easy enough.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As to using the feature layer of the Survey123, you got to pay attention to your form's schema. Working for my previous employer, I created a complex S123 form that fed the data daily into a PBI report. Between S123 and PBI, I used an ETL tool (FME Desktop) that stored the form data into SQL Server. If you have access to ArcGIS Pro you can use its DataInterop extension to do the same. You have options.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Jan 2020 14:47:13 GMT</pubDate>
    <dc:creator>RenatoSalvaleon3</dc:creator>
    <dc:date>2020-01-17T14:47:13Z</dc:date>
    <item>
      <title>survey 123 and Power BI</title>
      <link>https://community.esri.com/t5/arcgis-for-power-bi-questions/survey-123-and-power-bi/m-p/764059#M44</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;Has anyone tried to visualize Survey 123 form (tabular) data form the hosted feature service in Power BI? It sounds like the functionality is not there yet to directly view a feature layer's attribute table. Has anyone tried a workaround like developing a data export process that runs nightly so the tabular data can be displayed in a power BI dashboard? Maybe it's time to try esri Insights?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Renee&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Aug 2019 15:33:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-for-power-bi-questions/survey-123-and-power-bi/m-p/764059#M44</guid>
      <dc:creator>ReneeOpatz</dc:creator>
      <dc:date>2019-08-16T15:33:02Z</dc:date>
    </item>
    <item>
      <title>Re: survey 123 and Power BI</title>
      <link>https://community.esri.com/t5/arcgis-for-power-bi-questions/survey-123-and-power-bi/m-p/764060#M45</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Upvote this idea &lt;A _jive_internal="true" href="https://community.esri.com/ideas/13853-arcgis-data-connection-for-power-bi"&gt;https://community.esri.com/ideas/13853-arcgis-data-connection-for-power-bi&lt;/A&gt;. In that idea is a user comment that suggests a&amp;nbsp;workaround. If your form is simple enough (no repeats or attachments) and if you are good at JSON transformation using DAX and PQE, it should be easy enough.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As to using the feature layer of the Survey123, you got to pay attention to your form's schema. Working for my previous employer, I created a complex S123 form that fed the data daily into a PBI report. Between S123 and PBI, I used an ETL tool (FME Desktop) that stored the form data into SQL Server. If you have access to ArcGIS Pro you can use its DataInterop extension to do the same. You have options.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jan 2020 14:47:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-for-power-bi-questions/survey-123-and-power-bi/m-p/764060#M45</guid>
      <dc:creator>RenatoSalvaleon3</dc:creator>
      <dc:date>2020-01-17T14:47:13Z</dc:date>
    </item>
  </channel>
</rss>

