<?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>ChrisCB Tracker</title>
    <link>https://community.fabric.microsoft.com/t5/s/yrjkf47658/tracker</link>
    <description>ChrisCB Tracker</description>
    <pubDate>Sat, 19 Sep 2026 19:40:55 GMT</pubDate>
    <dc:date>2026-09-19T19:40:55Z</dc:date>
    <item>
      <title>Re: Providing Credentials to ODBC via CredentialsConnectionString option in Odbc.query and for files</title>
      <link>https://community.fabric.microsoft.com/t5/Power-Query/Providing-Credentials-to-ODBC-via-CredentialsConnectionString/m-p/3106539#M99266</link>
      <description>&lt;P&gt;This is such a bad answer, and overall a terrible policy. There are so many situations where a report writer might need to distribute a report to non-technical users (who get scared by things like the word "Credentials") which needs to connect to a data source. There are plenty of other solutions outside of excel to secure such a flow, such as using a limited read-only account on a SQL Server that replicates production. My users don't want to bother with credentials, and they shouldn't have to.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Mar 2023 19:41:46 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Power-Query/Providing-Credentials-to-ODBC-via-CredentialsConnectionString/m-p/3106539#M99266</guid>
      <dc:creator>ChrisCB</dc:creator>
      <dc:date>2023-03-01T19:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: Where to store my personal library of custom functions</title>
      <link>https://community.fabric.microsoft.com/t5/Power-Query/Where-to-store-my-personal-library-of-custom-functions/m-p/3099127#M98956</link>
      <description>&lt;P&gt;Anonymous&lt;/LI-USER&gt;&lt;/P&gt;&lt;P&gt;No offense but that's an extremely poor solution. No version control, no diff, no lint, and its even a hassle for reusability. One should be able to start a blank project, import some version controlled text files and move on with their lives.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This being for M and DAX code specifically, but lets be honest, everything inside PBI is likely in some xml schema or another, there's no reason to limit code/visualization reuse to literal PBI template files. What is this, a circa 1998 excel macro library?&lt;/P&gt;</description>
      <pubDate>Sat, 25 Feb 2023 04:53:49 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Power-Query/Where-to-store-my-personal-library-of-custom-functions/m-p/3099127#M98956</guid>
      <dc:creator>ChrisCB</dc:creator>
      <dc:date>2023-02-25T04:53:49Z</dc:date>
    </item>
    <item>
      <title>Re: Syntax Highlighting for M (how-to)</title>
      <link>https://community.fabric.microsoft.com/t5/Desktop/Syntax-Highlighting-for-M-how-to/m-p/3080693#M1045428</link>
      <description>&lt;P&gt;Quick Addition, if you want to add melpa and install fsharp-mode at the same time, add this to your .emacs (init.el) file:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN class=""&gt;;;; Initialize MELPA&lt;/SPAN&gt;
(&lt;SPAN class=""&gt;require&lt;/SPAN&gt; &lt;SPAN class=""&gt;'package&lt;/SPAN&gt;)
(&lt;SPAN class=""&gt;add-to-list&lt;/SPAN&gt; &lt;SPAN class=""&gt;'package-archives&lt;/SPAN&gt; '(&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;"&lt;/SPAN&gt;melpa&lt;SPAN class=""&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;.&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;"&lt;/SPAN&gt;http://melpa.org/packages/&lt;SPAN class=""&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt;))
(&lt;SPAN class=""&gt;unless&lt;/SPAN&gt; package-archive-contents (&lt;SPAN class=""&gt;package-refresh-contents&lt;/SPAN&gt;))
(&lt;SPAN class=""&gt;package-initialize&lt;/SPAN&gt;)

&lt;SPAN class=""&gt;;;; Install fsharp-mode&lt;/SPAN&gt;
(&lt;SPAN class=""&gt;unless&lt;/SPAN&gt; (&lt;SPAN class=""&gt;package-installed-p&lt;/SPAN&gt; &lt;SPAN class=""&gt;'fsharp-mode&lt;/SPAN&gt;)
  (&lt;SPAN class=""&gt;package-install&lt;/SPAN&gt; &lt;SPAN class=""&gt;'fsharp-mode&lt;/SPAN&gt;))

(&lt;SPAN class=""&gt;require&lt;/SPAN&gt; &lt;SPAN class=""&gt;'fsharp-mode&lt;/SPAN&gt;)&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Per the &lt;A href="https://github.com/fsharp/emacs-fsharp-mode" target="_blank" rel="noopener"&gt;github repository&lt;/A&gt; (which has other install methods for use-package and others).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks very much for the tip Anonymous&lt;/LI-USER&gt;, I've never used F# so this never would have occurred to me. Finally I can halfway escape the woefully inadequate power query "advanced" editor.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2023 04:43:55 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Desktop/Syntax-Highlighting-for-M-how-to/m-p/3080693#M1045428</guid>
      <dc:creator>ChrisCB</dc:creator>
      <dc:date>2023-02-15T04:43:55Z</dc:date>
    </item>
  </channel>
</rss>

