Skip to main content
sarahmiracle
sarahmiracle
VIP ⭐️⭐️⭐️⭐️⭐️
July 21, 2023
New Idea

Allow for inserting Null values in case expressions

Related products:CS Other Features
  • July 21, 2023
  • 15 replies
  • 216 views

It would be great if we could insert Null values for Case Expressions. The current configuration requires us to provide a value, even if that value is a Custom value.

Use Case:

  • I’m calculating an “Age” field for a professional services project. If the project is still Active, I want to insert my calculated Project Age field. If the project is not still Active, then I want a Null value. 

I can’t accomplish this use case as Case Expressions require a value.

    15 replies

    Show previous replies
    benwanlessmenlo
    benwanlessmenlo
    Contributor ⭐️⭐️⭐️⭐️⭐️
    October 10, 2024

    Let’s do data right. Please allow us to work with null valued fields.

      dayn.johnson
      dayn.johnson
      VIP ⭐️⭐️⭐️⭐️⭐️
      October 11, 2024

      Let’s do data right. Please allow us to work with null valued fields.

      Especially when we have to build evaluate steps to check for null data (and that data is null).

      Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
      alizee
      alizee
      VIP ⭐️⭐️⭐️⭐️⭐️
      October 11, 2024

      I’m upvoting….and in the meantime I’ve previous tackled this with a very poor work-around.

      1. Create a custom field in an object. The sole purpose of this custom field is to be a Null. No default values, no rules to populate. It literally just sits there.
      2. Pull that custom field into your fetch. Then in your CASE statement, when you need the Null, you “populate” your CASE statement by pointing at that custom field.

      I agree that the product could ideally do this as Sarah proposes, but if you really need it now, you’ve got a work-around.

      Thank you, Matthew, smart but sad :). Guess I’m going for that… MEH. MEH. MEH. MEH. MEH. 

      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.
        matthew_lind
        matthew_lind
        VIP ⭐️⭐️⭐️⭐️⭐️
        October 11, 2024

         

        I’m upvoting….and in the meantime I’ve previous tackled this with a very poor work-around.

        1. Create a custom field in an object. The sole purpose of this custom field is to be a Null. No default values, no rules to populate. It literally just sits there.
        2. Pull that custom field into your fetch. Then in your CASE statement, when you need the Null, you “populate” your CASE statement by pointing at that custom field.

        I agree that the product could ideally do this as Sarah proposes, but if you really need it now, you’ve got a work-around.

        Thank you, Matthew, smart but sad :). Guess I’m going for that… MEH. MEH. MEH. MEH. MEH. 

        @alizee I’m remarkably talented at “Smart but Sad”, in oh-so-many ways.

        Making people their best....currently disguised as a CS Ops Architect. How can I contribute to your success?
          alizee
          alizee
          VIP ⭐️⭐️⭐️⭐️⭐️
          October 14, 2024

           

          I’m upvoting….and in the meantime I’ve previous tackled this with a very poor work-around.

          1. Create a custom field in an object. The sole purpose of this custom field is to be a Null. No default values, no rules to populate. It literally just sits there.
          2. Pull that custom field into your fetch. Then in your CASE statement, when you need the Null, you “populate” your CASE statement by pointing at that custom field.

          I agree that the product could ideally do this as Sarah proposes, but if you really need it now, you’ve got a work-around.

          Thank you, Matthew, smart but sad :). Guess I’m going for that… MEH. MEH. MEH. MEH. MEH. 

          @alizee I’m remarkably talented at “Smart but Sad”, in oh-so-many ways.

          In the land of boolean nulls, smart but sad workarounds are life saviors, and those who invent them are warriors of the light.

          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