<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>RANK_MODIFIED on Bitfern</title>
    <link>/tags/rank_modified/</link>
    <description>Recent content in RANK_MODIFIED on Bitfern</description>
    <generator>Hugo</generator>
    <language>en-nz</language>
    <lastBuildDate>Fri, 31 Jan 2025 11:05:24 +0000</lastBuildDate>
    <atom:link href="/tags/rank_modified/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LOD equivalent of INDEX and RANK (part 2)</title>
      <link>/blog/lod-equivalent-of-index-2/</link>
      <pubDate>Fri, 31 Jan 2025 11:05:24 +0000</pubDate>
      <guid>/blog/lod-equivalent-of-index-2/</guid>
      <description>&lt;p&gt;In my last blog post I looked at a &lt;a href=&#34;/blog/lod-equivalent-of-index/&#34; title=&#34;LOD equivalent of INDEX&#34;&gt;LOD equivalent of RANK / INDEX table calculations in Tableau&lt;/a&gt;. That approach was limited to ranking a very small range of whole numbers, and left me considering other options. This post outlines another LOD approach using spatial functions**!**&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; As before I will stress that you should rarely need a LOD-based equivalent of rank or index, and can often use table calculations when you don’t think that you can. That said, there are scenarios where a LOD equivalent can be useful: onward use of the calc or use in spatial functions being the cases I’ve seen on the Tableau community forums. And it’s also a fun challenge!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
