Skip to main content
alizee
alizee
VIP ⭐️⭐️⭐️⭐️⭐️
March 30, 2023
New Idea

Allow non 'a-z' characters in output headers

Related products:CS Reports
  • March 30, 2023
  • 3 replies
  • 77 views

I’ve run into one of these silly limitations when pivoting a data set that contains product versions in a dropdown. Said versions start with a number, i.e. 6.10.1 (main, dot, micro) and when pivoting that data set on the version dropdown, I couldn’t save my pivot because… it had to start with a letter. 

Generally speaking - can we allow output headers and labels to start with numbers?

It’s really silly to have to add a letter in each column (in my case, 42), especially if we later want to append other information looking at versions. 

    3 replies

    alizee
    alizeeAuthor
    VIP ⭐️⭐️⭐️⭐️⭐️
    April 18, 2023

    Just want to add another example of this: I brought in the Unified Scorecard Fact - company object, and cannot save because the object name (standard object) contains a hyphen and the output header cannot. It should support hyphens and some degree of special characters on top of numbers.

     

    The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
      alizee
      alizeeAuthor
      VIP ⭐️⭐️⭐️⭐️⭐️
      April 19, 2023

      Another one: if I bring in the field “User”, that exists as such, why would I get an error message that the name “user” is reserved and I can’t use it. There needs to be a mechanism to auto-update the names in these instances or just, working around the fact the name is reserved (why is it, because there is no lookup to modified by/created by automatically added to a DD). 

       

      The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
        alizee
        alizeeAuthor
        VIP ⭐️⭐️⭐️⭐️⭐️
        August 22, 2025

        This has peaked now that I’ve had to label my field:

        One - EXP(- (N_in_W / tau_const)

        Instead of just what it does, aka: subtract EXP(- (N_in_W / tau_const) from 1, so:

        1 - EXP(- (N_in_W / tau_const). 

         

        (And yes, with this kind of build, I prefer the field name to be a description of the formula so when I have to add half a dozen transforms because functions can’t be nested in numeric expressions in one step, my formula still looks like the complete calculation). 

         

         

        The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
          Terms & ConditionsAccessibility statement