<?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 Mapping Issue with tExtractDynamicFields Component in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Mapping-Issue-with-tExtractDynamicFields-Component/m-p/2496222#M141613</link>
    <description>&lt;P&gt;Hi Qlik Community,&lt;/P&gt;
&lt;P&gt;I am currently working on a test job to illustrate a problem I am facing. I have an Excel file with four columns, one of which is named "Straße/Hausnr". Using the tExtractDynamicFields component, I aim to map the columns from the dynamic schema of the Excel component to a target column named "Strasse_Hausnr".&lt;/P&gt;
&lt;P&gt;However, in the output of tLogRow_1, the value for "Straße/Hausnr" is always null. The mapping of the columns is supposed to occur based on the matching of the Excel column names with the column names configured in the schema. Unfortunately, I am unable to get the value to map correctly.&lt;/P&gt;
&lt;P&gt;I understand that I could change the column name in the Excel file, but the data is provided to me in this format. How can I resolve this issue so that the Excel column "Straße/Hausnr" maps correctly to "Strasse_Hausnr"? Is there a naming convention on how the columns of the source are allowed to be named?&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The job setup is described in the attached PDF.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Thank you for your assistance!&lt;/P&gt;
&lt;P&gt;Best regards, &lt;BR /&gt;Josef&lt;/P&gt;</description>
    <pubDate>Thu, 05 Dec 2024 11:09:34 GMT</pubDate>
    <dc:creator>jpronebner</dc:creator>
    <dc:date>2024-12-05T11:09:34Z</dc:date>
    <item>
      <title>Mapping Issue with tExtractDynamicFields Component</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Mapping-Issue-with-tExtractDynamicFields-Component/m-p/2496222#M141613</link>
      <description>&lt;P&gt;Hi Qlik Community,&lt;/P&gt;
&lt;P&gt;I am currently working on a test job to illustrate a problem I am facing. I have an Excel file with four columns, one of which is named "Straße/Hausnr". Using the tExtractDynamicFields component, I aim to map the columns from the dynamic schema of the Excel component to a target column named "Strasse_Hausnr".&lt;/P&gt;
&lt;P&gt;However, in the output of tLogRow_1, the value for "Straße/Hausnr" is always null. The mapping of the columns is supposed to occur based on the matching of the Excel column names with the column names configured in the schema. Unfortunately, I am unable to get the value to map correctly.&lt;/P&gt;
&lt;P&gt;I understand that I could change the column name in the Excel file, but the data is provided to me in this format. How can I resolve this issue so that the Excel column "Straße/Hausnr" maps correctly to "Strasse_Hausnr"? Is there a naming convention on how the columns of the source are allowed to be named?&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The job setup is described in the attached PDF.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Thank you for your assistance!&lt;/P&gt;
&lt;P&gt;Best regards, &lt;BR /&gt;Josef&lt;/P&gt;</description>
      <pubDate>Thu, 05 Dec 2024 11:09:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Mapping-Issue-with-tExtractDynamicFields-Component/m-p/2496222#M141613</guid>
      <dc:creator>jpronebner</dc:creator>
      <dc:date>2024-12-05T11:09:34Z</dc:date>
    </item>
    <item>
      <title>Re: Mapping Issue with tExtractDynamicFields Component</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Mapping-Issue-with-tExtractDynamicFields-Component/m-p/2542128#M149391</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;tExtractDynamicFields works by resolving dynamic fields at runtime and placing them into a single Dynamic column. It does not automatically expand dynamic attributes into individual schema columns.&lt;/P&gt;&lt;P&gt;This behavior is expected and often appears as a mapping issue when using dynamic schemas.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Recommended approach&lt;/STRONG&gt;:&lt;/P&gt;&lt;P&gt;Define one Dynamic column in the output schema of tExtractDynamicFields.&lt;/P&gt;&lt;P&gt;Keep any required static columns separately.&lt;/P&gt;&lt;P&gt;Extract or map individual dynamic values downstream using tMap, tNormalize, or custom logic.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Note&lt;/STRONG&gt;:&lt;BR /&gt;Dynamic schemas are designed for flexible data structures. Explicit field extraction must be handled after the dynamic column is populated.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Gourav&lt;/P&gt;</description>
      <pubDate>Sun, 01 Feb 2026 20:37:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Mapping-Issue-with-tExtractDynamicFields-Component/m-p/2542128#M149391</guid>
      <dc:creator>gouravdubey5</dc:creator>
      <dc:date>2026-02-01T20:37:06Z</dc:date>
    </item>
  </channel>
</rss>

