<?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: Passing parameter in Fabric ADF pipeline in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Passing-parameter-in-Fabric-ADF-pipeline/m-p/4397724#M6988</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="903432" data-lia-user-login="girishtharwani2" class="lia-mention lia-mention-user"&gt;girishtharwani2&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We appreciate your inquiry through the Microsoft Fabric Community Forum.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Fabric does not directly support the same parameter-passing mechanisms as ADF/Synapse when setting up scheduled triggers. Instead, it utilises the default values defined in the pipeline parameters.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;To implement parameters in a Fabric ADF pipeline, please follow the steps below:&lt;/SPAN&gt;&lt;/P&gt;
&lt;OL start="1" data-spread="false"&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN&gt;Navigate to the pipeline's Parameters tab and set the necessary default values for the parameters. Once the default values are set, they will be used whenever a schedule is activated.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN&gt;If feasible, use activities within the original pipeline that can read from a dataset or a lookup, which provides the necessary parameters to facilitate dynamic transformation or data movement.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;SPAN&gt;In Fabric, triggers exist solely as a pipeline concept. The broader framework that pipeline triggers utilise in Fabric is known as Data Activator, which is an event and alerting subsystem of the Real-time Intelligence features in Fabric. Scheduled triggers are a separate entity in Fabric and are referred to as schedules. These schedules function at a platform level in Fabric and are not specific to pipelines. Moreover, they are not referred to as triggers in Fabric.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Additionally, please refer to the following link:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/fabric/data-factory/parameters" target="_blank"&gt;Parameters - Microsoft Fabric | Microsoft Learn&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members facing similar queries.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 06 Feb 2025 07:26:18 GMT</pubDate>
    <dc:creator>v-pnaroju-msft</dc:creator>
    <dc:date>2025-02-06T07:26:18Z</dc:date>
    <item>
      <title>Passing parameter in Fabric ADF pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Passing-parameter-in-Fabric-ADF-pipeline/m-p/4396816#M6964</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When creating a Schedule in Fabric thats all there is (see below screenshot). After clicking apply the schedule is set.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In ADF/Synapse after clicking commit for a trigger (which btw also can be named which is not possible in Fabric) one gets asked about the trigger specific values for the pipelines defined parameters:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to implement it in Fabric ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Girish&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Feb 2025 16:49:44 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Passing-parameter-in-Fabric-ADF-pipeline/m-p/4396816#M6964</guid>
      <dc:creator>girishtharwani2</dc:creator>
      <dc:date>2025-02-05T16:49:44Z</dc:date>
    </item>
    <item>
      <title>Re: Passing parameter in Fabric ADF pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Passing-parameter-in-Fabric-ADF-pipeline/m-p/4397724#M6988</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="903432" data-lia-user-login="girishtharwani2" class="lia-mention lia-mention-user"&gt;girishtharwani2&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We appreciate your inquiry through the Microsoft Fabric Community Forum.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Fabric does not directly support the same parameter-passing mechanisms as ADF/Synapse when setting up scheduled triggers. Instead, it utilises the default values defined in the pipeline parameters.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;To implement parameters in a Fabric ADF pipeline, please follow the steps below:&lt;/SPAN&gt;&lt;/P&gt;
&lt;OL start="1" data-spread="false"&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN&gt;Navigate to the pipeline's Parameters tab and set the necessary default values for the parameters. Once the default values are set, they will be used whenever a schedule is activated.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN&gt;If feasible, use activities within the original pipeline that can read from a dataset or a lookup, which provides the necessary parameters to facilitate dynamic transformation or data movement.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;SPAN&gt;In Fabric, triggers exist solely as a pipeline concept. The broader framework that pipeline triggers utilise in Fabric is known as Data Activator, which is an event and alerting subsystem of the Real-time Intelligence features in Fabric. Scheduled triggers are a separate entity in Fabric and are referred to as schedules. These schedules function at a platform level in Fabric and are not specific to pipelines. Moreover, they are not referred to as triggers in Fabric.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Additionally, please refer to the following link:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/fabric/data-factory/parameters" target="_blank"&gt;Parameters - Microsoft Fabric | Microsoft Learn&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members facing similar queries.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Feb 2025 07:26:18 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Passing-parameter-in-Fabric-ADF-pipeline/m-p/4397724#M6988</guid>
      <dc:creator>v-pnaroju-msft</dc:creator>
      <dc:date>2025-02-06T07:26:18Z</dc:date>
    </item>
    <item>
      <title>Re: Passing parameter in Fabric ADF pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Passing-parameter-in-Fabric-ADF-pipeline/m-p/4401271#M7066</link>
      <description>&lt;P&gt;Thanks for answering, appreciate it.&lt;/P&gt;</description>
      <pubDate>Sun, 09 Feb 2025 05:43:48 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Passing-parameter-in-Fabric-ADF-pipeline/m-p/4401271#M7066</guid>
      <dc:creator>girishtharwani2</dc:creator>
      <dc:date>2025-02-09T05:43:48Z</dc:date>
    </item>
  </channel>
</rss>

