<?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 New bugs in Developer Tools in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/New-bugs-in-Developer-Tools/m-p/22382#M381</link>
    <description>&lt;P&gt;Hi everybody,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found two bugs in the Power BI Developer Tools (tested with&amp;nbsp;Chrome and Edge):&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;when you export a new visual the first time, no&amp;nbsp;images are included. You have to export it again and re-attach icon, screenshot and thumbnail to build&amp;nbsp;a complete package;&lt;/LI&gt;&lt;LI&gt;when you fill Privacy or License url field and export you visual, the online tool produce an invalid package that you can't import in Power BI Desktop (because an invalid string in &lt;STRONG&gt;package.json&lt;/STRONG&gt; file, embedded in the visual itself). Avoid to&amp;nbsp;fill that fields&amp;nbsp;and remember that if&amp;nbsp;you made that mistake,&amp;nbsp;it's not sufficient to empty the fields, you have to delete entirely the custom visual and then re-create it. Alternatively you can open the PBIVIZ file with WinZip (or a similar tool) and manually edit package.json removing the offending strings.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 09 Mar 2016 09:31:24 GMT</pubDate>
    <dc:creator>danieleperilli</dc:creator>
    <dc:date>2016-03-09T09:31:24Z</dc:date>
    <item>
      <title>New bugs in Developer Tools</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/New-bugs-in-Developer-Tools/m-p/22382#M381</link>
      <description>&lt;P&gt;Hi everybody,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found two bugs in the Power BI Developer Tools (tested with&amp;nbsp;Chrome and Edge):&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;when you export a new visual the first time, no&amp;nbsp;images are included. You have to export it again and re-attach icon, screenshot and thumbnail to build&amp;nbsp;a complete package;&lt;/LI&gt;&lt;LI&gt;when you fill Privacy or License url field and export you visual, the online tool produce an invalid package that you can't import in Power BI Desktop (because an invalid string in &lt;STRONG&gt;package.json&lt;/STRONG&gt; file, embedded in the visual itself). Avoid to&amp;nbsp;fill that fields&amp;nbsp;and remember that if&amp;nbsp;you made that mistake,&amp;nbsp;it's not sufficient to empty the fields, you have to delete entirely the custom visual and then re-create it. Alternatively you can open the PBIVIZ file with WinZip (or a similar tool) and manually edit package.json removing the offending strings.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 09:31:24 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/New-bugs-in-Developer-Tools/m-p/22382#M381</guid>
      <dc:creator>danieleperilli</dc:creator>
      <dc:date>2016-03-09T09:31:24Z</dc:date>
    </item>
    <item>
      <title>Re: New bugs in Developer Tools</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/New-bugs-in-Developer-Tools/m-p/22743#M394</link>
      <description>&lt;P&gt;Hey thanks for reporting this issue. We're aware of this and are looking into a fix. A current workaround is to not include a privacy link and licence link. Stay tuned for an update!&lt;/P&gt;</description>
      <pubDate>Fri, 11 Mar 2016 04:43:18 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/New-bugs-in-Developer-Tools/m-p/22743#M394</guid>
      <dc:creator>Wes</dc:creator>
      <dc:date>2016-03-11T04:43:18Z</dc:date>
    </item>
  </channel>
</rss>

