nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

REQUEST: Are we looking into any method of adding CF based on a non-numeric?

erik.bangsund

Boolean T/F
List Formatted LI = Specific List Item

@eschera : Boolean would be great. Bonus points for being able to leverage a separate (systems) module to drive conditional formatting.

Comments

There are no comments yet

Quick Links

New ideas

Does Anaplan XL offer a free trial?
Hi team, I’m interested in exploring Anaplan XL and would like to know whether a free trial or trial version is available for users to evaluate its features and functionality. If available, could you please share the process or requirements to access the trial? Thanks in advance!
Pivoting line items to the context selector in UX is exposing all line items from the backend module
When a line item is pivoted from rows or columns to the context selector on UX, it always shows all line items in the module in context selector, regardless of whether it is Classic or Polaris. This exposes all backend line items in the module.
AXL Reporting - Query Rendering Logic - Check Suppression First
AXL Reporting has suppression options to suppress rows and columns but the problem is that these settings are AFTER query rendering. In example below there are only 15 rows of filled data but the query indicates a huge number of cells are needed. The enhancement needed here is to first check user suppression settings on…