We currently have cube where we needed to split the first rule into multiple rules, once split and saved the rule the expected change is not shown. Tracing the rule still shows the old rule logic in it. Can confirm the .rux file matches the rule that I have in my rules editor with the expected rule in there. I have restarted the instance, reloaded the cube, closed my browser cleared the cache and still getting the same result. We then created a new element created a rule for it when opening it at a view at the lowest level there is no rule applied to cell.

Any ideas what can be causing this?

Example of rule that we split:

Original "[ 'Version':'Actual', 'Time Analysis':'BASE', 'Channel':'No Channel', 'Sales Forecast Measures':{ 'Predictive Sales QTY', 'Allocated Forecast Sales QTY' } ] =  N: "

New  "[ 'Version':'Actual', 'Time Analysis':'BASE', Channel':'No Channel', Sales Forecast Measures':'Predictive Sales QTY' ] =  N: "

"[ 'Version':'Actual', 'Time Analysis':'BASE', 'Channel':'No Channel', ' Sales Forecast Measures': 'Allocated Forecast Sales QTY'  ] =  N:"

Hello!

1. It's not Friday evening, but: are you completely sure it's same instance, same server you are changing and checking the rule? :)
2. Where are you changing the rule? Is it showing any errors? Try another rule editor (eg if you are changing it in PAW, try Architect)
3. Try to clear the rule completely. If it takes effect, than there is error in your rule, but rule editor does not show it for some reason.\

Hi Pieter,

Thanks for the detailed explanation - it sounds like you've already taken the right steps in troubleshooting (restarting the instance, reloading the cube, clearing cache, etc.).

Here are a few things you might want to check:

1. Rule Propagation: Sometimes when rules are edited or split, the new logic might not propagate correctly until a full metadata refresh is performed. Try restarting the TM1 server (not just the instance) if you haven't already.

2. Rule Order or Conflicts: Ensure that there are no other conflicting rules later in the file that may be overriding your changes. Also, double-check for any formatting or syntax issues, especially when splitting similar logic into multiple lines.

3. Dimension Aliases or Spacing: Look out for extra spaces or inconsistencies in dimension element names - e.g., ' Sales Forecast Measures' (note the space before the element name in your second rule) could cause it to not trigger.

4. Security or Cell Data Status: Confirm that the cells at the lowest level aren't secured or marked as input-disabled, which might prevent the rule from applying visibly even if it's technically there.

5. Cube View Filters: In the new element where you created the rule, make sure the view is not filtered or sliced in a way that hides the cell where the rule should apply.

As an analogy, think of it like setting different product banners for specific items - if you're managing several categories like tunic dress collections on harwage.pk, you'd expect each rule or template to show specific content. If the backend isn't syncing properly, what you preview won't reflect what you set - same with rules in TM1.

George Tonkin has a correct answer but he is too shy to answer: "not all dims have a leading apostrophe, single quote e.g. channel - TM1 is probably taking everything from after Channel': onwards to the next quote as a reference..."

Hi,

good advice so far, however this

1. Rule Order or Conflicts: Ensure that there are no other conflicting rules later in the file that may be overriding your changes. Also, double-check for any formatting or syntax issues, especially when splitting similar logic into multiple lines.

I assume this should read 'earlier in the file' rather than later. I.e. we assume you Pieter has commented out the old rule and not added any new rules which may affect these cells?

If all else fails, you could try deleting all the BLB files after you stop the server, as I swear I have seen issues around this in the past.

regards,

Mark

Hi,

the last sentence is something that came to my mind as well: Alongside the rux file, there might be a blb file, that contains the rules as well with rules editor format information. To my information, this overrides the rux files, so in case both files differ, you still have the old setting from the blb file applied to the cube. 

If that is actually not the case anymore, I'd appreciate if someone tells me. 🙂

But maybe don't delete all blb files, as they could contain view information as well.

Kind regards
Matthias

------------------------------
Matthias Holthus
------------------------------