Uncommitted Work Pending - Working around DML then WebService












3














I am working with Salesforce Connect and I am storing my token and expiration times in an encrypted custom setting. My connection is through the client credentials Oauth 2 flow.



When a user queries an external object, it makes sense to me in the initial method of salesforce connect DataSource.Connection class to:




  1. Update the custom settings fields if there is no information or the
    token has expired.


  2. Use the custom settings to get the access token if the token has not expired.



This would be fine, however within the same transaction, in the query method of the DataSource.Connection class, webservice callouts to fetch the external objects with the newly updated token must occur. This results in an "uncommitted work pending" error as we would expect because webservice callouts cannot be made after DML statements.



Future methods don't seem to be a plausible solution here because if the token is expired I need those custom settings to be updated at that time otherwise the rest callout will fail.



I thought calling a new instance of another class with a method to update the custom setting might be considered a new transactions, but my assumption was wrong.



I could have users request a token every rest call and store them within the class and not within the custom setting, but that seems so absurdly excessive where as the custom setting would allow multiple users to utilize the same token and only make a token callout when necessary since it's a client connection anyways.



Recommendations?






rest-api webservices oauth2 dml salesforce-connect







share|improve this question



























    3














    I am working with Salesforce Connect and I am storing my token and expiration times in an encrypted custom setting. My connection is through the client credentials Oauth 2 flow.



    When a user queries an external object, it makes sense to me in the initial method of salesforce connect DataSource.Connection class to:




    1. Update the custom settings fields if there is no information or the
      token has expired.


    2. Use the custom settings to get the access token if the token has not expired.



    This would be fine, however within the same transaction, in the query method of the DataSource.Connection class, webservice callouts to fetch the external objects with the newly updated token must occur. This results in an "uncommitted work pending" error as we would expect because webservice callouts cannot be made after DML statements.



    Future methods don't seem to be a plausible solution here because if the token is expired I need those custom settings to be updated at that time otherwise the rest callout will fail.



    I thought calling a new instance of another class with a method to update the custom setting might be considered a new transactions, but my assumption was wrong.



    I could have users request a token every rest call and store them within the class and not within the custom setting, but that seems so absurdly excessive where as the custom setting would allow multiple users to utilize the same token and only make a token callout when necessary since it's a client connection anyways.



    Recommendations?






    rest-api webservices oauth2 dml salesforce-connect







    share|improve this question

























      3












      3








      3







      I am working with Salesforce Connect and I am storing my token and expiration times in an encrypted custom setting. My connection is through the client credentials Oauth 2 flow.



      When a user queries an external object, it makes sense to me in the initial method of salesforce connect DataSource.Connection class to:




      1. Update the custom settings fields if there is no information or the
        token has expired.


      2. Use the custom settings to get the access token if the token has not expired.



      This would be fine, however within the same transaction, in the query method of the DataSource.Connection class, webservice callouts to fetch the external objects with the newly updated token must occur. This results in an "uncommitted work pending" error as we would expect because webservice callouts cannot be made after DML statements.



      Future methods don't seem to be a plausible solution here because if the token is expired I need those custom settings to be updated at that time otherwise the rest callout will fail.



      I thought calling a new instance of another class with a method to update the custom setting might be considered a new transactions, but my assumption was wrong.



      I could have users request a token every rest call and store them within the class and not within the custom setting, but that seems so absurdly excessive where as the custom setting would allow multiple users to utilize the same token and only make a token callout when necessary since it's a client connection anyways.



      Recommendations?






      rest-api webservices oauth2 dml salesforce-connect







      share|improve this question













      I am working with Salesforce Connect and I am storing my token and expiration times in an encrypted custom setting. My connection is through the client credentials Oauth 2 flow.



      When a user queries an external object, it makes sense to me in the initial method of salesforce connect DataSource.Connection class to:




      1. Update the custom settings fields if there is no information or the
        token has expired.


      2. Use the custom settings to get the access token if the token has not expired.



      This would be fine, however within the same transaction, in the query method of the DataSource.Connection class, webservice callouts to fetch the external objects with the newly updated token must occur. This results in an "uncommitted work pending" error as we would expect because webservice callouts cannot be made after DML statements.



      Future methods don't seem to be a plausible solution here because if the token is expired I need those custom settings to be updated at that time otherwise the rest callout will fail.



      I thought calling a new instance of another class with a method to update the custom setting might be considered a new transactions, but my assumption was wrong.



      I could have users request a token every rest call and store them within the class and not within the custom setting, but that seems so absurdly excessive where as the custom setting would allow multiple users to utilize the same token and only make a token callout when necessary since it's a client connection anyways.



      Recommendations?






      rest-api webservices oauth2 dml salesforce-connect




      rest-api webservices oauth2 dml salesforce-connect






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 5 hours ago









      S.B.

      42319




      42319






















          1 Answer
          1






          active

          oldest

          votes


















          4















          I could have users request a token every rest call and store them within the class and not within the custom setting




          You can take the advantages of both approaches. Set up your callout so you can use a token from within memory. If you need to update your setting, move that DML to the end of your transaction.



          Pseudo-code:



          String token = MySetting__c.getOrgDefaults__c.Token__c;
          

          
// if the token is blank or expired, get a new one
          
// and reassign the value in your token variable
          

          
// make your callout using the valid token
          

          
// if the token was blank or expired, update your setting





          share|improve this answer





















          • Now that's what I call thinking. Thanks!
            – S.B.
            4 hours ago











          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',
          autoActivateHeartbeat: false,
          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%2f244825%2funcommitted-work-pending-working-around-dml-then-webservice%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









          4















          I could have users request a token every rest call and store them within the class and not within the custom setting




          You can take the advantages of both approaches. Set up your callout so you can use a token from within memory. If you need to update your setting, move that DML to the end of your transaction.



          Pseudo-code:



          String token = MySetting__c.getOrgDefaults__c.Token__c;
          

          
// if the token is blank or expired, get a new one
          
// and reassign the value in your token variable
          

          
// make your callout using the valid token
          

          
// if the token was blank or expired, update your setting





          share|improve this answer





















          • Now that's what I call thinking. Thanks!
            – S.B.
            4 hours ago
















          4















          I could have users request a token every rest call and store them within the class and not within the custom setting




          You can take the advantages of both approaches. Set up your callout so you can use a token from within memory. If you need to update your setting, move that DML to the end of your transaction.



          Pseudo-code:



          String token = MySetting__c.getOrgDefaults__c.Token__c;
          

          
// if the token is blank or expired, get a new one
          
// and reassign the value in your token variable
          

          
// make your callout using the valid token
          

          
// if the token was blank or expired, update your setting





          share|improve this answer





















          • Now that's what I call thinking. Thanks!
            – S.B.
            4 hours ago














          4












          4








          4







          I could have users request a token every rest call and store them within the class and not within the custom setting




          You can take the advantages of both approaches. Set up your callout so you can use a token from within memory. If you need to update your setting, move that DML to the end of your transaction.



          Pseudo-code:



          String token = MySetting__c.getOrgDefaults__c.Token__c;
          

          
// if the token is blank or expired, get a new one
          
// and reassign the value in your token variable
          

          
// make your callout using the valid token
          

          
// if the token was blank or expired, update your setting





          share|improve this answer













          I could have users request a token every rest call and store them within the class and not within the custom setting




          You can take the advantages of both approaches. Set up your callout so you can use a token from within memory. If you need to update your setting, move that DML to the end of your transaction.



          Pseudo-code:



          String token = MySetting__c.getOrgDefaults__c.Token__c;
          

          
// if the token is blank or expired, get a new one
          
// and reassign the value in your token variable
          

          
// make your callout using the valid token
          

          
// if the token was blank or expired, update your setting






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 4 hours ago









          Adrian Larson♦

          104k19112235




          104k19112235












          • Now that's what I call thinking. Thanks!
            – S.B.
            4 hours ago


















          • Now that's what I call thinking. Thanks!
            – S.B.
            4 hours ago
















          Now that's what I call thinking. Thanks!
          – S.B.
          4 hours ago




          Now that's what I call thinking. Thanks!
          – S.B.
          4 hours ago


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Salesforce Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f244825%2funcommitted-work-pending-working-around-dml-then-webservice%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

          404 Error Contact Form 7 ajax form submitting

          Image
          0 The contact form does not work, and affects loading after one try. The chrome console shows the error message: POST http://example.com/wp-json/contact-form-7/v1/contact-forms/50/feedback 404 (Not Found) send @ jquery.js?ver=1.12.4:4 ajax @ jquery.js?ver=1.12.4:4 wpcf7.submit @ scripts.js?ver=5.0.3:346 (anonymous) @ scripts.js?ver=5.0.3:53 dispatch @ jquery.js?ver=1.12.4:3 r.handle @ jquery.js?ver=1.12.4:3 How to solve this issue? thanks in advance javascript wordpress contact-form-7 share | improve this question edited Jul 17 '18 at 5:39 Kiran Shahi 4,745 3 16 43 ...
          Read more

          How to know if a Active Directory user can login interactively

          Image
          1 I would like to know if and how is it possible to know if a AD user can login interactively (on a server) in a domain. I need to know if I can find it out using a LDAP search. Thanks. windows active-directory login user-permissions user-profile share | improve this question edited 1 hour ago yagmoth555 ♦ 11.6k 3 17 42 asked 1 hour ago Luigi Luigi 6 1 New contributor ...
          Read more

          Refactoring coordinates for Minecraft Pi buildings written in Python

          Image
          0 $begingroup$ I'm fairly new to coding and I wrote this script in Python for a house with a roof in Minecraft Pi. I've found different ways to write the coordinates to make the code base shorter, but I'm wondering if it is possible for me to refactor it any further so I don't have to list each coordinate line by line. import mcpi.minecraft as minecraft import mcpi.block as block mc = minecraft.Minecraft.create() p = mc.player.getTilePos() mc.setBlocks(p.x+1, p.y, p.z+1, #Main structure starting coordinates (DO NOT ALTER) p.x+19, p.y+4, p.z+6, #Structure size/coordinates (Alters cube size) block.STONE_BRICK) mc.setBlocks(p.x+2, p.y+1, p.z+2, #Hollowing out main structure interior p.x+18, p.y+3, p.z+5, block.AIR) mc.setBlocks(p.x, p.y...
          Read more