Add a Protected Range to an existing NamedRange

Multi tool use
Multi tool use












3















I have an existing worksheet with an existing NamedRange for it and I would like to call the batch_update method of the API to protect that range from being edited by anyone other than the user that makes the batch_update call.



I have seen an example on how to add protected ranges via a new range definition, but not from an existing NamedRange.



I know I need to send the addProtectedRangeResponse request. Can I define the request body with a Sheetname!NamedRange notation?



this_range = worksheet_name + "!" + nrange
batch_update_spreadsheet_request_body = {
'requests': [
{
"addProtectedRange": {
"protectedRange": {
"range": {
"name": this_range,
},
"description": "Protecting xyz",
"warningOnly": False
}
}
}
],
}


EDIT: Given @Tanaike feedback, I adapted the call to something like:



        body = {
"requests": [
{
"addProtectedRange": {
"protectedRange": {
"namedRangeId": namedRangeId,
"description": "Protecting via gsheets_manager",
"warningOnly": False,
"requestingUserCanEdit": False
}
}
}
]
}
res2 = service.spreadsheets().batchUpdate(spreadsheetId=ssId, body=body).execute()
print(res2)


But although it lists the new protections, it still lists 5 different users (all of them) as editors. If I try to manually edit the protection added by my gsheets_manager script, it complains that the range is invalid:



enter image description here



Interestingly, it seems to ignore the requestUserCanEdit flag according to the returning message:



{u'spreadsheetId': u'NNNNNNNNNNNNNNNNNNNNNNNNNNNN', u'replies': [{u'addProtectedRange': {u'protectedRange': {u'requestingUserCanEdit': True, u'description': u'Protecting via gsheets_manager', u'namedRangeId': u'1793914032', u'editors': {}, u'protectedRangeId': 2012740267, u'range': {u'endColumnIndex': 1, u'sheetId': 1196959832, u'startColumnIndex': 0}}}}]}



Any ideas?










share|improve this question





























    3















    I have an existing worksheet with an existing NamedRange for it and I would like to call the batch_update method of the API to protect that range from being edited by anyone other than the user that makes the batch_update call.



    I have seen an example on how to add protected ranges via a new range definition, but not from an existing NamedRange.



    I know I need to send the addProtectedRangeResponse request. Can I define the request body with a Sheetname!NamedRange notation?



    this_range = worksheet_name + "!" + nrange
    batch_update_spreadsheet_request_body = {
    'requests': [
    {
    "addProtectedRange": {
    "protectedRange": {
    "range": {
    "name": this_range,
    },
    "description": "Protecting xyz",
    "warningOnly": False
    }
    }
    }
    ],
    }


    EDIT: Given @Tanaike feedback, I adapted the call to something like:



            body = {
    "requests": [
    {
    "addProtectedRange": {
    "protectedRange": {
    "namedRangeId": namedRangeId,
    "description": "Protecting via gsheets_manager",
    "warningOnly": False,
    "requestingUserCanEdit": False
    }
    }
    }
    ]
    }
    res2 = service.spreadsheets().batchUpdate(spreadsheetId=ssId, body=body).execute()
    print(res2)


    But although it lists the new protections, it still lists 5 different users (all of them) as editors. If I try to manually edit the protection added by my gsheets_manager script, it complains that the range is invalid:



    enter image description here



    Interestingly, it seems to ignore the requestUserCanEdit flag according to the returning message:



    {u'spreadsheetId': u'NNNNNNNNNNNNNNNNNNNNNNNNNNNN', u'replies': [{u'addProtectedRange': {u'protectedRange': {u'requestingUserCanEdit': True, u'description': u'Protecting via gsheets_manager', u'namedRangeId': u'1793914032', u'editors': {}, u'protectedRangeId': 2012740267, u'range': {u'endColumnIndex': 1, u'sheetId': 1196959832, u'startColumnIndex': 0}}}}]}



    Any ideas?










    share|improve this question



























      3












      3








      3








      I have an existing worksheet with an existing NamedRange for it and I would like to call the batch_update method of the API to protect that range from being edited by anyone other than the user that makes the batch_update call.



      I have seen an example on how to add protected ranges via a new range definition, but not from an existing NamedRange.



      I know I need to send the addProtectedRangeResponse request. Can I define the request body with a Sheetname!NamedRange notation?



      this_range = worksheet_name + "!" + nrange
      batch_update_spreadsheet_request_body = {
      'requests': [
      {
      "addProtectedRange": {
      "protectedRange": {
      "range": {
      "name": this_range,
      },
      "description": "Protecting xyz",
      "warningOnly": False
      }
      }
      }
      ],
      }


      EDIT: Given @Tanaike feedback, I adapted the call to something like:



              body = {
      "requests": [
      {
      "addProtectedRange": {
      "protectedRange": {
      "namedRangeId": namedRangeId,
      "description": "Protecting via gsheets_manager",
      "warningOnly": False,
      "requestingUserCanEdit": False
      }
      }
      }
      ]
      }
      res2 = service.spreadsheets().batchUpdate(spreadsheetId=ssId, body=body).execute()
      print(res2)


      But although it lists the new protections, it still lists 5 different users (all of them) as editors. If I try to manually edit the protection added by my gsheets_manager script, it complains that the range is invalid:



      enter image description here



      Interestingly, it seems to ignore the requestUserCanEdit flag according to the returning message:



      {u'spreadsheetId': u'NNNNNNNNNNNNNNNNNNNNNNNNNNNN', u'replies': [{u'addProtectedRange': {u'protectedRange': {u'requestingUserCanEdit': True, u'description': u'Protecting via gsheets_manager', u'namedRangeId': u'1793914032', u'editors': {}, u'protectedRangeId': 2012740267, u'range': {u'endColumnIndex': 1, u'sheetId': 1196959832, u'startColumnIndex': 0}}}}]}



      Any ideas?










      share|improve this question
















      I have an existing worksheet with an existing NamedRange for it and I would like to call the batch_update method of the API to protect that range from being edited by anyone other than the user that makes the batch_update call.



      I have seen an example on how to add protected ranges via a new range definition, but not from an existing NamedRange.



      I know I need to send the addProtectedRangeResponse request. Can I define the request body with a Sheetname!NamedRange notation?



      this_range = worksheet_name + "!" + nrange
      batch_update_spreadsheet_request_body = {
      'requests': [
      {
      "addProtectedRange": {
      "protectedRange": {
      "range": {
      "name": this_range,
      },
      "description": "Protecting xyz",
      "warningOnly": False
      }
      }
      }
      ],
      }


      EDIT: Given @Tanaike feedback, I adapted the call to something like:



              body = {
      "requests": [
      {
      "addProtectedRange": {
      "protectedRange": {
      "namedRangeId": namedRangeId,
      "description": "Protecting via gsheets_manager",
      "warningOnly": False,
      "requestingUserCanEdit": False
      }
      }
      }
      ]
      }
      res2 = service.spreadsheets().batchUpdate(spreadsheetId=ssId, body=body).execute()
      print(res2)


      But although it lists the new protections, it still lists 5 different users (all of them) as editors. If I try to manually edit the protection added by my gsheets_manager script, it complains that the range is invalid:



      enter image description here



      Interestingly, it seems to ignore the requestUserCanEdit flag according to the returning message:



      {u'spreadsheetId': u'NNNNNNNNNNNNNNNNNNNNNNNNNNNN', u'replies': [{u'addProtectedRange': {u'protectedRange': {u'requestingUserCanEdit': True, u'description': u'Protecting via gsheets_manager', u'namedRangeId': u'1793914032', u'editors': {}, u'protectedRangeId': 2012740267, u'range': {u'endColumnIndex': 1, u'sheetId': 1196959832, u'startColumnIndex': 0}}}}]}



      Any ideas?







      python google-sheets google-sheets-api google-api-python-client






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 3 at 10:09







      719016

















      asked Jan 2 at 11:36









      719016719016

      2,8721156114




      2,8721156114
























          1 Answer
          1






          active

          oldest

          votes


















          1














          How about using namedRangeId for your situation? The flow of the sample script is as follows.




          1. Retrieve namedRangeId using spreadsheets().get of Sheets API.

          2. Set a protected range using namedRangeId using spreadsheets().batchUpdate of Sheets API.


          Sample script:



          nrange = "### name ###"
          ssId = "### spreadsheetId ###"

          res1 = service.spreadsheets().get(spreadsheetId=ssId, fields="namedRanges").execute()
          namedRangeId = ""
          for e in res1['namedRanges']:
          if e['name'] == nrange:
          namedRangeId = e['namedRangeId']
          break
          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False
          }
          }
          }
          ]
          }
          res2 = service.spreadsheets().batchUpdate(spreadsheetId=ssId, body=body).execute()
          print(res2)


          Note:




          • This script supposes that Sheets API can be used for your environment.

          • This is a simple sample script. So please modify it to your situation.


          References:




          • ProtectedRange

          • Named and Protected Ranges


          If this was not what you want, I'm sorry.



          Edit:



          In my above answer, I modified your script using your settings. If you want to protect the named range, please modify body as follows.



          Modified body

          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False,
          "editors": {"users": ["### your email address ###"]}, # Added
          }
          }
          }
          ]
          }


          By this, the named range can be modified by only you. I'm using such settings and I confirm that it works in my environment. But if in your situation, this didn't work, I'm sorry.






          share|improve this answer





















          • 1





            @719016 Thank you for replying. I'm really sorry for the inconvenience and my incomplete answer. I updated my answer. Could you please confirm it?

            – Tanaike
            Jan 3 at 23:24






          • 1





            @tehhowch Thank you for your support.

            – Tanaike
            Jan 3 at 23:24






          • 1





            @719016 Did my answer show you the result what you want? Would you please tell me about it? That is also useful for me to study. If this works, other people who have the same issue with you can also base your question as a question which can be solved. If you have issues for my answer yet, feel free to tell me. I would like to study to solve your issues.

            – Tanaike
            Jan 4 at 23:30






          • 1





            @719016 Is there anything that I can do for your question? If my answer was not useful for your situation. I have to apologize and modify it.

            – Tanaike
            Jan 6 at 22:01






          • 1





            It now works as per the answer in @Tanaike post. The addition of the email addresses made all the difference. Thanks very much for you help!

            – 719016
            Jan 7 at 10:22











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fstackoverflow.com%2fquestions%2f54005634%2fadd-a-protected-range-to-an-existing-namedrange%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









          1














          How about using namedRangeId for your situation? The flow of the sample script is as follows.




          1. Retrieve namedRangeId using spreadsheets().get of Sheets API.

          2. Set a protected range using namedRangeId using spreadsheets().batchUpdate of Sheets API.


          Sample script:



          nrange = "### name ###"
          ssId = "### spreadsheetId ###"

          res1 = service.spreadsheets().get(spreadsheetId=ssId, fields="namedRanges").execute()
          namedRangeId = ""
          for e in res1['namedRanges']:
          if e['name'] == nrange:
          namedRangeId = e['namedRangeId']
          break
          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False
          }
          }
          }
          ]
          }
          res2 = service.spreadsheets().batchUpdate(spreadsheetId=ssId, body=body).execute()
          print(res2)


          Note:




          • This script supposes that Sheets API can be used for your environment.

          • This is a simple sample script. So please modify it to your situation.


          References:




          • ProtectedRange

          • Named and Protected Ranges


          If this was not what you want, I'm sorry.



          Edit:



          In my above answer, I modified your script using your settings. If you want to protect the named range, please modify body as follows.



          Modified body

          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False,
          "editors": {"users": ["### your email address ###"]}, # Added
          }
          }
          }
          ]
          }


          By this, the named range can be modified by only you. I'm using such settings and I confirm that it works in my environment. But if in your situation, this didn't work, I'm sorry.






          share|improve this answer





















          • 1





            @719016 Thank you for replying. I'm really sorry for the inconvenience and my incomplete answer. I updated my answer. Could you please confirm it?

            – Tanaike
            Jan 3 at 23:24






          • 1





            @tehhowch Thank you for your support.

            – Tanaike
            Jan 3 at 23:24






          • 1





            @719016 Did my answer show you the result what you want? Would you please tell me about it? That is also useful for me to study. If this works, other people who have the same issue with you can also base your question as a question which can be solved. If you have issues for my answer yet, feel free to tell me. I would like to study to solve your issues.

            – Tanaike
            Jan 4 at 23:30






          • 1





            @719016 Is there anything that I can do for your question? If my answer was not useful for your situation. I have to apologize and modify it.

            – Tanaike
            Jan 6 at 22:01






          • 1





            It now works as per the answer in @Tanaike post. The addition of the email addresses made all the difference. Thanks very much for you help!

            – 719016
            Jan 7 at 10:22
















          1














          How about using namedRangeId for your situation? The flow of the sample script is as follows.




          1. Retrieve namedRangeId using spreadsheets().get of Sheets API.

          2. Set a protected range using namedRangeId using spreadsheets().batchUpdate of Sheets API.


          Sample script:



          nrange = "### name ###"
          ssId = "### spreadsheetId ###"

          res1 = service.spreadsheets().get(spreadsheetId=ssId, fields="namedRanges").execute()
          namedRangeId = ""
          for e in res1['namedRanges']:
          if e['name'] == nrange:
          namedRangeId = e['namedRangeId']
          break
          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False
          }
          }
          }
          ]
          }
          res2 = service.spreadsheets().batchUpdate(spreadsheetId=ssId, body=body).execute()
          print(res2)


          Note:




          • This script supposes that Sheets API can be used for your environment.

          • This is a simple sample script. So please modify it to your situation.


          References:




          • ProtectedRange

          • Named and Protected Ranges


          If this was not what you want, I'm sorry.



          Edit:



          In my above answer, I modified your script using your settings. If you want to protect the named range, please modify body as follows.



          Modified body

          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False,
          "editors": {"users": ["### your email address ###"]}, # Added
          }
          }
          }
          ]
          }


          By this, the named range can be modified by only you. I'm using such settings and I confirm that it works in my environment. But if in your situation, this didn't work, I'm sorry.






          share|improve this answer





















          • 1





            @719016 Thank you for replying. I'm really sorry for the inconvenience and my incomplete answer. I updated my answer. Could you please confirm it?

            – Tanaike
            Jan 3 at 23:24






          • 1





            @tehhowch Thank you for your support.

            – Tanaike
            Jan 3 at 23:24






          • 1





            @719016 Did my answer show you the result what you want? Would you please tell me about it? That is also useful for me to study. If this works, other people who have the same issue with you can also base your question as a question which can be solved. If you have issues for my answer yet, feel free to tell me. I would like to study to solve your issues.

            – Tanaike
            Jan 4 at 23:30






          • 1





            @719016 Is there anything that I can do for your question? If my answer was not useful for your situation. I have to apologize and modify it.

            – Tanaike
            Jan 6 at 22:01






          • 1





            It now works as per the answer in @Tanaike post. The addition of the email addresses made all the difference. Thanks very much for you help!

            – 719016
            Jan 7 at 10:22














          1












          1








          1







          How about using namedRangeId for your situation? The flow of the sample script is as follows.




          1. Retrieve namedRangeId using spreadsheets().get of Sheets API.

          2. Set a protected range using namedRangeId using spreadsheets().batchUpdate of Sheets API.


          Sample script:



          nrange = "### name ###"
          ssId = "### spreadsheetId ###"

          res1 = service.spreadsheets().get(spreadsheetId=ssId, fields="namedRanges").execute()
          namedRangeId = ""
          for e in res1['namedRanges']:
          if e['name'] == nrange:
          namedRangeId = e['namedRangeId']
          break
          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False
          }
          }
          }
          ]
          }
          res2 = service.spreadsheets().batchUpdate(spreadsheetId=ssId, body=body).execute()
          print(res2)


          Note:




          • This script supposes that Sheets API can be used for your environment.

          • This is a simple sample script. So please modify it to your situation.


          References:




          • ProtectedRange

          • Named and Protected Ranges


          If this was not what you want, I'm sorry.



          Edit:



          In my above answer, I modified your script using your settings. If you want to protect the named range, please modify body as follows.



          Modified body

          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False,
          "editors": {"users": ["### your email address ###"]}, # Added
          }
          }
          }
          ]
          }


          By this, the named range can be modified by only you. I'm using such settings and I confirm that it works in my environment. But if in your situation, this didn't work, I'm sorry.






          share|improve this answer















          How about using namedRangeId for your situation? The flow of the sample script is as follows.




          1. Retrieve namedRangeId using spreadsheets().get of Sheets API.

          2. Set a protected range using namedRangeId using spreadsheets().batchUpdate of Sheets API.


          Sample script:



          nrange = "### name ###"
          ssId = "### spreadsheetId ###"

          res1 = service.spreadsheets().get(spreadsheetId=ssId, fields="namedRanges").execute()
          namedRangeId = ""
          for e in res1['namedRanges']:
          if e['name'] == nrange:
          namedRangeId = e['namedRangeId']
          break
          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False
          }
          }
          }
          ]
          }
          res2 = service.spreadsheets().batchUpdate(spreadsheetId=ssId, body=body).execute()
          print(res2)


          Note:




          • This script supposes that Sheets API can be used for your environment.

          • This is a simple sample script. So please modify it to your situation.


          References:




          • ProtectedRange

          • Named and Protected Ranges


          If this was not what you want, I'm sorry.



          Edit:



          In my above answer, I modified your script using your settings. If you want to protect the named range, please modify body as follows.



          Modified body

          body = {
          "requests": [
          {
          "addProtectedRange": {
          "protectedRange": {
          "namedRangeId": namedRangeId,
          "description": "Protecting xyz",
          "warningOnly": False,
          "editors": {"users": ["### your email address ###"]}, # Added
          }
          }
          }
          ]
          }


          By this, the named range can be modified by only you. I'm using such settings and I confirm that it works in my environment. But if in your situation, this didn't work, I'm sorry.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 3 at 23:23

























          answered Jan 2 at 23:36









          TanaikeTanaike

          23.2k21124




          23.2k21124








          • 1





            @719016 Thank you for replying. I'm really sorry for the inconvenience and my incomplete answer. I updated my answer. Could you please confirm it?

            – Tanaike
            Jan 3 at 23:24






          • 1





            @tehhowch Thank you for your support.

            – Tanaike
            Jan 3 at 23:24






          • 1





            @719016 Did my answer show you the result what you want? Would you please tell me about it? That is also useful for me to study. If this works, other people who have the same issue with you can also base your question as a question which can be solved. If you have issues for my answer yet, feel free to tell me. I would like to study to solve your issues.

            – Tanaike
            Jan 4 at 23:30






          • 1





            @719016 Is there anything that I can do for your question? If my answer was not useful for your situation. I have to apologize and modify it.

            – Tanaike
            Jan 6 at 22:01






          • 1





            It now works as per the answer in @Tanaike post. The addition of the email addresses made all the difference. Thanks very much for you help!

            – 719016
            Jan 7 at 10:22














          • 1





            @719016 Thank you for replying. I'm really sorry for the inconvenience and my incomplete answer. I updated my answer. Could you please confirm it?

            – Tanaike
            Jan 3 at 23:24






          • 1





            @tehhowch Thank you for your support.

            – Tanaike
            Jan 3 at 23:24






          • 1





            @719016 Did my answer show you the result what you want? Would you please tell me about it? That is also useful for me to study. If this works, other people who have the same issue with you can also base your question as a question which can be solved. If you have issues for my answer yet, feel free to tell me. I would like to study to solve your issues.

            – Tanaike
            Jan 4 at 23:30






          • 1





            @719016 Is there anything that I can do for your question? If my answer was not useful for your situation. I have to apologize and modify it.

            – Tanaike
            Jan 6 at 22:01






          • 1





            It now works as per the answer in @Tanaike post. The addition of the email addresses made all the difference. Thanks very much for you help!

            – 719016
            Jan 7 at 10:22








          1




          1





          @719016 Thank you for replying. I'm really sorry for the inconvenience and my incomplete answer. I updated my answer. Could you please confirm it?

          – Tanaike
          Jan 3 at 23:24





          @719016 Thank you for replying. I'm really sorry for the inconvenience and my incomplete answer. I updated my answer. Could you please confirm it?

          – Tanaike
          Jan 3 at 23:24




          1




          1





          @tehhowch Thank you for your support.

          – Tanaike
          Jan 3 at 23:24





          @tehhowch Thank you for your support.

          – Tanaike
          Jan 3 at 23:24




          1




          1





          @719016 Did my answer show you the result what you want? Would you please tell me about it? That is also useful for me to study. If this works, other people who have the same issue with you can also base your question as a question which can be solved. If you have issues for my answer yet, feel free to tell me. I would like to study to solve your issues.

          – Tanaike
          Jan 4 at 23:30





          @719016 Did my answer show you the result what you want? Would you please tell me about it? That is also useful for me to study. If this works, other people who have the same issue with you can also base your question as a question which can be solved. If you have issues for my answer yet, feel free to tell me. I would like to study to solve your issues.

          – Tanaike
          Jan 4 at 23:30




          1




          1





          @719016 Is there anything that I can do for your question? If my answer was not useful for your situation. I have to apologize and modify it.

          – Tanaike
          Jan 6 at 22:01





          @719016 Is there anything that I can do for your question? If my answer was not useful for your situation. I have to apologize and modify it.

          – Tanaike
          Jan 6 at 22:01




          1




          1





          It now works as per the answer in @Tanaike post. The addition of the email addresses made all the difference. Thanks very much for you help!

          – 719016
          Jan 7 at 10:22





          It now works as per the answer in @Tanaike post. The addition of the email addresses made all the difference. Thanks very much for you help!

          – 719016
          Jan 7 at 10:22




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • 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%2fstackoverflow.com%2fquestions%2f54005634%2fadd-a-protected-range-to-an-existing-namedrange%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







          43,0h2WsFC1oRRqPfGWbiZACNY6SYaw,Yj7ZPm
          3l5aeGDeE,D1CavcFqzm4Hi QC,qtos0UNoe9PPvp,yKQr f GwWd51dzsk1,6H

          Popular posts from this blog

          Monofisismo

          Angular Downloading a file using contenturl with Basic Authentication

          Olmecas