Is there a typesafe way to work with rowCause?





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






up vote
1
down vote

favorite












On the project I'm currently working with, we have Apex Sharing Rules.
I see we are passing rowCause as a String everywhere.
But the values of these Strings look like API names.



Is there a typesafe way we can work with these?










share|improve this question




























    up vote
    1
    down vote

    favorite












    On the project I'm currently working with, we have Apex Sharing Rules.
    I see we are passing rowCause as a String everywhere.
    But the values of these Strings look like API names.



    Is there a typesafe way we can work with these?










    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      On the project I'm currently working with, we have Apex Sharing Rules.
      I see we are passing rowCause as a String everywhere.
      But the values of these Strings look like API names.



      Is there a typesafe way we can work with these?










      share|improve this question













      On the project I'm currently working with, we have Apex Sharing Rules.
      I see we are passing rowCause as a String everywhere.
      But the values of these Strings look like API names.



      Is there a typesafe way we can work with these?







      apex api apex-managed-sharing sharing-rule type






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 1 hour ago









      Brian Kessler

      1,4711131




      1,4711131






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote













          Refer this documentation: Sharing a Record Using Apex



          Apex sharing reasons are defined on an object's detail page. Each Apex sharing reason has a label and a name:




          • The label displays in the Reason column when viewing the sharing for a record in the user interface. This label allows users and administrators to understand the source of the sharing. The label is also enabled for translation through the Translation Workbench.

          • The name is used when referencing the reason in the API and Apex.


          All Apex sharing reason names have the following format:
          MyReasonName__c



          Apex sharing reasons can be referenced programmatically as follows:



          Schema.CustomObject__Share.rowCause.SharingReason__c


          For example, an Apex sharing reason called Recruiter for an object called Job can be referenced as follows:



          Schema.Job__Share.rowCause.Recruiter__c



          So, sharing reason must be used which you have defined and that's why it takes API name. It always hold String value.







          share|improve this answer





















            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: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            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%2f240417%2fis-there-a-typesafe-way-to-work-with-rowcause%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote













            Refer this documentation: Sharing a Record Using Apex



            Apex sharing reasons are defined on an object's detail page. Each Apex sharing reason has a label and a name:




            • The label displays in the Reason column when viewing the sharing for a record in the user interface. This label allows users and administrators to understand the source of the sharing. The label is also enabled for translation through the Translation Workbench.

            • The name is used when referencing the reason in the API and Apex.


            All Apex sharing reason names have the following format:
            MyReasonName__c



            Apex sharing reasons can be referenced programmatically as follows:



            Schema.CustomObject__Share.rowCause.SharingReason__c


            For example, an Apex sharing reason called Recruiter for an object called Job can be referenced as follows:



            Schema.Job__Share.rowCause.Recruiter__c



            So, sharing reason must be used which you have defined and that's why it takes API name. It always hold String value.







            share|improve this answer

























              up vote
              2
              down vote













              Refer this documentation: Sharing a Record Using Apex



              Apex sharing reasons are defined on an object's detail page. Each Apex sharing reason has a label and a name:




              • The label displays in the Reason column when viewing the sharing for a record in the user interface. This label allows users and administrators to understand the source of the sharing. The label is also enabled for translation through the Translation Workbench.

              • The name is used when referencing the reason in the API and Apex.


              All Apex sharing reason names have the following format:
              MyReasonName__c



              Apex sharing reasons can be referenced programmatically as follows:



              Schema.CustomObject__Share.rowCause.SharingReason__c


              For example, an Apex sharing reason called Recruiter for an object called Job can be referenced as follows:



              Schema.Job__Share.rowCause.Recruiter__c



              So, sharing reason must be used which you have defined and that's why it takes API name. It always hold String value.







              share|improve this answer























                up vote
                2
                down vote










                up vote
                2
                down vote









                Refer this documentation: Sharing a Record Using Apex



                Apex sharing reasons are defined on an object's detail page. Each Apex sharing reason has a label and a name:




                • The label displays in the Reason column when viewing the sharing for a record in the user interface. This label allows users and administrators to understand the source of the sharing. The label is also enabled for translation through the Translation Workbench.

                • The name is used when referencing the reason in the API and Apex.


                All Apex sharing reason names have the following format:
                MyReasonName__c



                Apex sharing reasons can be referenced programmatically as follows:



                Schema.CustomObject__Share.rowCause.SharingReason__c


                For example, an Apex sharing reason called Recruiter for an object called Job can be referenced as follows:



                Schema.Job__Share.rowCause.Recruiter__c



                So, sharing reason must be used which you have defined and that's why it takes API name. It always hold String value.







                share|improve this answer












                Refer this documentation: Sharing a Record Using Apex



                Apex sharing reasons are defined on an object's detail page. Each Apex sharing reason has a label and a name:




                • The label displays in the Reason column when viewing the sharing for a record in the user interface. This label allows users and administrators to understand the source of the sharing. The label is also enabled for translation through the Translation Workbench.

                • The name is used when referencing the reason in the API and Apex.


                All Apex sharing reason names have the following format:
                MyReasonName__c



                Apex sharing reasons can be referenced programmatically as follows:



                Schema.CustomObject__Share.rowCause.SharingReason__c


                For example, an Apex sharing reason called Recruiter for an object called Job can be referenced as follows:



                Schema.Job__Share.rowCause.Recruiter__c



                So, sharing reason must be used which you have defined and that's why it takes API name. It always hold String value.








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 50 mins ago









                Santanu Boral

                29.6k52151




                29.6k52151






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f240417%2fis-there-a-typesafe-way-to-work-with-rowcause%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    What visual should I use to simply compare current year value vs last year in Power BI desktop

                    Alexandru Averescu

                    Trompette piccolo