I believe that I have found a bug, but wanted to check this by the Community to see if I'm missing something or if there are some additional creative workarounds that we could employ in the future. I've created a simple illustration of what we are encountering for the screenshots below, but what we are doing in reality is on a larger scale.
It seems that formulas do not adhere as expected to subset formatting. For instance, I have the below module dimensioned by a list "Company". There are two line items: "Geos Mapping" where a manual assignment is made of exactly one item from the Geos list to every item in the Company list and "Geos Lookup - Excluding EMEA" where I want to only pull through from Geos Mapping where the selected Geos item is not in a particular subset (namely, a subset I created that includes all members of the Geos list except for EMEA).
I would expect that EMEA does not show up in "Geos Lookup - Excluding EMEA" as it is formatted as the subset that excludes EMA. However, it disregards the fact that the subset excludes that item and populates in every case.
Workaround: Add in IF/THEN logic with a LOOKUP - can be completely formulaic and gets to the expected answer
Since we do have a workaround, we are able to continue for now. But I am curious as to if others have encountered a similar issue and what workarounds you employed. And, of course, if I'm just doing something wrong and it's an easy fix then let me know
Solved! Go to Solution.
It seems to be a bug. Its better to raise a ticket with Anaplan and highlight this to Support team so that it will be considered in 'Future Roadmap'.
My workaround would be using finditem function instead of writing a condition. Ex. FINDITEM('SUBSET',CODE('LINE ITEM')).
I hope this help!!
Hi @bdeaton ,
Another workaround can be :
Instead of referring to the Geos Mapping Line item,
Create a saved view and Import Geos Mapping line item into "Geos Lookup - Excluding EMEA" formatted as the subset that excludes EMEA.