<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Variables passed from ADF to Databricks Notebook Try-Catch are not accessible in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/variables-passed-from-adf-to-databricks-notebook-try-catch-are/m-p/66499#M33139</link>
    <description>&lt;P&gt;Parameters are defined in ADF and transferred to databricks so it is outside try catch&lt;/P&gt;</description>
    <pubDate>Wed, 17 Apr 2024 17:04:50 GMT</pubDate>
    <dc:creator>Abhi0607</dc:creator>
    <dc:date>2024-04-17T17:04:50Z</dc:date>
    <item>
      <title>Variables passed from ADF to Databricks Notebook Try-Catch are not accessible</title>
      <link>https://community.databricks.com/t5/data-engineering/variables-passed-from-adf-to-databricks-notebook-try-catch-are/m-p/66476#M33133</link>
      <description>&lt;P&gt;Dear Members,&lt;/P&gt;&lt;P&gt;I need your help in below scenario.&lt;/P&gt;&lt;P&gt;I am passing few parameters from ADF pipeline to Databricks notebook.&lt;/P&gt;&lt;P&gt;If I execute ADF pipeline to run my databricks notebook and use these variables as is in my code (python) then it works fine.&lt;/P&gt;&lt;P&gt;But as soon as I use Try and catch block in my notebook then these variables which are passed from ADF pipeline, it does not recognize these variables. I can still print value of those variables outside the Try-Catch block but not inside Try-Catch.&lt;/P&gt;&lt;P&gt;Can you please suggest how can I proceed or access the variables which are passed by ADF inside the Try-Catch blocks of databricks notebook?&lt;/P&gt;&lt;P&gt;Note: This issue happens only if I run my databricks notebook through ADF pipeline. If I assign values in notebooks and run standalone notebook then it works.&lt;/P&gt;&lt;P&gt;Thank you for your help!&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2024 14:18:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/variables-passed-from-adf-to-databricks-notebook-try-catch-are/m-p/66476#M33133</guid>
      <dc:creator>Abhi0607</dc:creator>
      <dc:date>2024-04-17T14:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: Variables passed from ADF to Databricks Notebook Try-Catch are not accessible</title>
      <link>https://community.databricks.com/t5/data-engineering/variables-passed-from-adf-to-databricks-notebook-try-catch-are/m-p/66481#M33135</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/103693"&gt;@Abhi0607&lt;/a&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please help me to find if you are taking or defining these parameter value outside try catch or inside it ?&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2024 14:18:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/variables-passed-from-adf-to-databricks-notebook-try-catch-are/m-p/66481#M33135</guid>
      <dc:creator>Ajay-Pandey</dc:creator>
      <dc:date>2024-04-17T14:18:42Z</dc:date>
    </item>
    <item>
      <title>Re: Variables passed from ADF to Databricks Notebook Try-Catch are not accessible</title>
      <link>https://community.databricks.com/t5/data-engineering/variables-passed-from-adf-to-databricks-notebook-try-catch-are/m-p/66499#M33139</link>
      <description>&lt;P&gt;Parameters are defined in ADF and transferred to databricks so it is outside try catch&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2024 17:04:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/variables-passed-from-adf-to-databricks-notebook-try-catch-are/m-p/66499#M33139</guid>
      <dc:creator>Abhi0607</dc:creator>
      <dc:date>2024-04-17T17:04:50Z</dc:date>
    </item>
  </channel>
</rss>

