Can ISNULL be used with custom settings in formula?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
1
down vote

favorite












I want to evaluate a workflow rule based on a custom setting value. The custom setting can be null so I want to check for isNULL before fetching the value of the custom settings field.



This is the formula I'm using



 AND(ISPICKVAL(Rating, "Closed Won"),
ISNULL($Setup.MySettings__c.notify__c))


This, however, returns a syntax error - "Error: Incorrect argument type for function 'ISNULL()'."



Is there any other way to check for Blank or null values for custom settings?










share|improve this question



























    up vote
    1
    down vote

    favorite












    I want to evaluate a workflow rule based on a custom setting value. The custom setting can be null so I want to check for isNULL before fetching the value of the custom settings field.



    This is the formula I'm using



     AND(ISPICKVAL(Rating, "Closed Won"),
    ISNULL($Setup.MySettings__c.notify__c))


    This, however, returns a syntax error - "Error: Incorrect argument type for function 'ISNULL()'."



    Is there any other way to check for Blank or null values for custom settings?










    share|improve this question























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I want to evaluate a workflow rule based on a custom setting value. The custom setting can be null so I want to check for isNULL before fetching the value of the custom settings field.



      This is the formula I'm using



       AND(ISPICKVAL(Rating, "Closed Won"),
      ISNULL($Setup.MySettings__c.notify__c))


      This, however, returns a syntax error - "Error: Incorrect argument type for function 'ISNULL()'."



      Is there any other way to check for Blank or null values for custom settings?










      share|improve this question













      I want to evaluate a workflow rule based on a custom setting value. The custom setting can be null so I want to check for isNULL before fetching the value of the custom settings field.



      This is the formula I'm using



       AND(ISPICKVAL(Rating, "Closed Won"),
      ISNULL($Setup.MySettings__c.notify__c))


      This, however, returns a syntax error - "Error: Incorrect argument type for function 'ISNULL()'."



      Is there any other way to check for Blank or null values for custom settings?







      formula customsetting custom






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked yesterday









      user1104

      63




      63




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          3
          down vote













          The problem isn't ISNULL (though ISBLANK is the recommendation for new fields), it's that checkbox fields won't ever return null. If the custom setting is null, any checkboxes on it will appear as a "false" value instead. As far as I can tell, there's no way to detect the difference between an unset checkbox and a set, but unchecked, checkbox.






          share|improve this answer



























            up vote
            0
            down vote













            Did you try this -



            AND(ISPICKVAL(Rating, "Closed Won"), $Setup.MySettings__c.notify__c)





            share|improve this answer


















            • 1




              Where Notify__c is a Boolean, there's no need to wrap it in an IF() to return true or false. Boolean fields will never be null.
              – David Reed
              yesterday










            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "459"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f232010%2fcan-isnull-be-used-with-custom-settings-in-formula%23new-answer', 'question_page');

            );

            Post as a guest






























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            3
            down vote













            The problem isn't ISNULL (though ISBLANK is the recommendation for new fields), it's that checkbox fields won't ever return null. If the custom setting is null, any checkboxes on it will appear as a "false" value instead. As far as I can tell, there's no way to detect the difference between an unset checkbox and a set, but unchecked, checkbox.






            share|improve this answer
























              up vote
              3
              down vote













              The problem isn't ISNULL (though ISBLANK is the recommendation for new fields), it's that checkbox fields won't ever return null. If the custom setting is null, any checkboxes on it will appear as a "false" value instead. As far as I can tell, there's no way to detect the difference between an unset checkbox and a set, but unchecked, checkbox.






              share|improve this answer






















                up vote
                3
                down vote










                up vote
                3
                down vote









                The problem isn't ISNULL (though ISBLANK is the recommendation for new fields), it's that checkbox fields won't ever return null. If the custom setting is null, any checkboxes on it will appear as a "false" value instead. As far as I can tell, there's no way to detect the difference between an unset checkbox and a set, but unchecked, checkbox.






                share|improve this answer












                The problem isn't ISNULL (though ISBLANK is the recommendation for new fields), it's that checkbox fields won't ever return null. If the custom setting is null, any checkboxes on it will appear as a "false" value instead. As far as I can tell, there's no way to detect the difference between an unset checkbox and a set, but unchecked, checkbox.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered yesterday









                sfdcfox

                226k10173388




                226k10173388






















                    up vote
                    0
                    down vote













                    Did you try this -



                    AND(ISPICKVAL(Rating, "Closed Won"), $Setup.MySettings__c.notify__c)





                    share|improve this answer


















                    • 1




                      Where Notify__c is a Boolean, there's no need to wrap it in an IF() to return true or false. Boolean fields will never be null.
                      – David Reed
                      yesterday














                    up vote
                    0
                    down vote













                    Did you try this -



                    AND(ISPICKVAL(Rating, "Closed Won"), $Setup.MySettings__c.notify__c)





                    share|improve this answer


















                    • 1




                      Where Notify__c is a Boolean, there's no need to wrap it in an IF() to return true or false. Boolean fields will never be null.
                      – David Reed
                      yesterday












                    up vote
                    0
                    down vote










                    up vote
                    0
                    down vote









                    Did you try this -



                    AND(ISPICKVAL(Rating, "Closed Won"), $Setup.MySettings__c.notify__c)





                    share|improve this answer














                    Did you try this -



                    AND(ISPICKVAL(Rating, "Closed Won"), $Setup.MySettings__c.notify__c)






                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited yesterday

























                    answered yesterday









                    Bennie

                    1,34611529




                    1,34611529







                    • 1




                      Where Notify__c is a Boolean, there's no need to wrap it in an IF() to return true or false. Boolean fields will never be null.
                      – David Reed
                      yesterday












                    • 1




                      Where Notify__c is a Boolean, there's no need to wrap it in an IF() to return true or false. Boolean fields will never be null.
                      – David Reed
                      yesterday







                    1




                    1




                    Where Notify__c is a Boolean, there's no need to wrap it in an IF() to return true or false. Boolean fields will never be null.
                    – David Reed
                    yesterday




                    Where Notify__c is a Boolean, there's no need to wrap it in an IF() to return true or false. Boolean fields will never be null.
                    – David Reed
                    yesterday

















                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f232010%2fcan-isnull-be-used-with-custom-settings-in-formula%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Comments

                    Popular posts from this blog

                    What does second last employer means? [closed]

                    List of Gilmore Girls characters

                    Confectionery