<?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>article Qlik Replicate: How to keep NUMERIC field precision and scale for PostgreSQL source endpoint in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/ta-p/2037219</link>
    <description>&lt;P&gt;&lt;SPAN&gt;When the source endpoint PostgreSQL Data Type is &lt;STRONG&gt;NUMERIC&lt;/STRONG&gt; (without precision/scale), it is map to &lt;STRONG&gt;NUMBER(28,6)&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp;, the decimal point maybe truncated. For example the source value&amp;nbsp;&lt;STRONG&gt;0.1234567890123456&lt;/STRONG&gt; will be truncated to&amp;nbsp;&lt;STRONG&gt;0.123456&lt;/STRONG&gt;&amp;nbsp;in target endpoint. This is Replicate and PostgreSQL default behavior, the data type mapping is in Replicate User Guide &lt;A title="PostgreSQL Data Types" href="https://help.qlik.com/en-US/replicate/November2022/Content/Replicate/Main/PostgreSQL/postgresql_data_types_source.htm#PostgreSQL%20source%20data%20types" target="_blank" rel="noopener"&gt;PostgreSQL Data Types&lt;/A&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;This article describes how to overcome the limitation and keep&amp;nbsp;NUMERIC field precision and scale.&lt;/P&gt;
&lt;H3 id="toc-hId--525314414"&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;Add an internal parameter to adjust PostgreSQL behavior:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Open&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;PostgreSQL source endpoint&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Go to the&amp;nbsp;&lt;STRONG&gt;Advanced&lt;/STRONG&gt;&amp;nbsp;tab&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Open&amp;nbsp;&lt;STRONG&gt;Internal Parameters&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Add a&lt;EM class="Highlight"&gt;&amp;nbsp;new&amp;nbsp;&lt;/EM&gt;parameter named&amp;nbsp;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;additionalConnectionProperties&lt;BR /&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;Press&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&amp;lt;Enter&amp;gt;&lt;/STRONG&gt;&amp;nbsp;and set the parameter's value to:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;BR /&gt;D6=12;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="internal parameter.png" style="width: 691px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/119463i2566F47981CBB12D/image-size/large?v=v2&amp;amp;px=999" role="button" title="internal parameter.png" alt="internal parameter.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Change the Type in table transformation, from &lt;/SPAN&gt;&lt;STRONG style="font-family: inherit;"&gt;STRING(1000)&lt;/STRONG&gt;&lt;SPAN&gt; to&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="font-family: inherit;"&gt;NUMERIC(28,16)&lt;/STRONG&gt;&lt;SPAN&gt;, or any other precision/scale you want. In the below sample, the column "nm" data type is&amp;nbsp;NUMERIC.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="table transformation.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/119464iDDB8A883B45B38CE/image-size/large?v=v2&amp;amp;px=999" role="button" title="table transformation.png" alt="table transformation.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Reload the task&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;H3 id="toc-hId-1962198419"&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Related Content&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;PostgreSQL ODBC Driver treats data type&amp;nbsp;&lt;STRONG&gt;Numeric(without precision) AS&lt;/STRONG&gt;&amp;nbsp;as "default" by default, change it to "varchar" then the NUMERIC will be parsed as STRING(1000). Replicate applies the implicit data type mapping from STRING(1000) to custom precision and scale.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; The parameter name in ODBC file is "&lt;STRONG&gt;D6&lt;/STRONG&gt;", it's values are:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;&lt;FONT face="courier new,courier"&gt;Default : -101&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;FONT face="courier new,courier"&gt;varchar : 12&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;FONT face="courier new,courier"&gt;double&amp;nbsp; : 8&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;FONT face="courier new,courier"&gt;memo&amp;nbsp; &amp;nbsp; : -1&lt;/FONT&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; In ODBC Manager it's:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="john_wang_6-1676298847544.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/100351i365BF708F556B64A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="john_wang_6-1676298847544.png" alt="john_wang_6-1676298847544.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3 id="toc-hId-1962198419"&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A id="hoverCardLink" class="lia-link-navigation lia-product-hover-card-link lia-product-mention lia-tooltip-trigger" href="https://community.qlik.com/t5/c-cyjdu72974/Qlik+Replicate/pd-p/qlikReplicate" target="_blank" rel="noopener"&gt;Qlik Replicate&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;nbsp; all versions&lt;BR /&gt;PostgreSQL&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;all Server versions (psqlODBC 11.00.0000 Release and above)&lt;/P&gt;
&lt;H3 id="toc-hId--993259818"&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Internal Investigation ID(s):&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Support cases, #00069371&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Feature Request &lt;A title="Add precision and scale for Postgresql source endpoint for numeric fields" href="https://ideation.qlik.com/app/#/case/281146" target="_blank" rel="noopener"&gt;Add precision and scale for Postgresql source endpoint for numeric fields&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A id="hoverCardLink" class="lia-link-navigation lia-product-hover-card-link lia-product-mention lia-tooltip-trigger" href="https://community.qlik.com/t5/c-cyjdu72974/Qlik+Replicate/pd-p/qlikReplicate" target="_blank" rel="noopener"&gt;Qlik Replicate&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Nov 2023 08:13:56 GMT</pubDate>
    <dc:creator>john_wang</dc:creator>
    <dc:date>2023-11-07T08:13:56Z</dc:date>
    <item>
      <title>Qlik Replicate: How to keep NUMERIC field precision and scale for PostgreSQL source endpoint</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/ta-p/2037219</link>
      <description>&lt;P&gt;&lt;SPAN&gt;When the source endpoint PostgreSQL Data Type is &lt;STRONG&gt;NUMERIC&lt;/STRONG&gt; (without precision/scale), it is map to &lt;STRONG&gt;NUMBER(28,6)&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp;, the decimal point maybe truncated. For example the source value&amp;nbsp;&lt;STRONG&gt;0.1234567890123456&lt;/STRONG&gt; will be truncated to&amp;nbsp;&lt;STRONG&gt;0.123456&lt;/STRONG&gt;&amp;nbsp;in target endpoint. This is Replicate and PostgreSQL default behavior, the data type mapping is in Replicate User Guide &lt;A title="PostgreSQL Data Types" href="https://help.qlik.com/en-US/replicate/November2022/Content/Replicate/Main/PostgreSQL/postgresql_data_types_source.htm#PostgreSQL%20source%20data%20types" target="_blank" rel="noopener"&gt;PostgreSQL Data Types&lt;/A&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;This article describes how to overcome the limitation and keep&amp;nbsp;NUMERIC field precision and scale.&lt;/P&gt;
&lt;H3 id="toc-hId--525314414"&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;Add an internal parameter to adjust PostgreSQL behavior:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Open&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;PostgreSQL source endpoint&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Go to the&amp;nbsp;&lt;STRONG&gt;Advanced&lt;/STRONG&gt;&amp;nbsp;tab&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Open&amp;nbsp;&lt;STRONG&gt;Internal Parameters&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Add a&lt;EM class="Highlight"&gt;&amp;nbsp;new&amp;nbsp;&lt;/EM&gt;parameter named&amp;nbsp;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;additionalConnectionProperties&lt;BR /&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;Press&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&amp;lt;Enter&amp;gt;&lt;/STRONG&gt;&amp;nbsp;and set the parameter's value to:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;BR /&gt;D6=12;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="internal parameter.png" style="width: 691px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/119463i2566F47981CBB12D/image-size/large?v=v2&amp;amp;px=999" role="button" title="internal parameter.png" alt="internal parameter.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Change the Type in table transformation, from &lt;/SPAN&gt;&lt;STRONG style="font-family: inherit;"&gt;STRING(1000)&lt;/STRONG&gt;&lt;SPAN&gt; to&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="font-family: inherit;"&gt;NUMERIC(28,16)&lt;/STRONG&gt;&lt;SPAN&gt;, or any other precision/scale you want. In the below sample, the column "nm" data type is&amp;nbsp;NUMERIC.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="table transformation.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/119464iDDB8A883B45B38CE/image-size/large?v=v2&amp;amp;px=999" role="button" title="table transformation.png" alt="table transformation.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Reload the task&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;H3 id="toc-hId-1962198419"&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Related Content&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;PostgreSQL ODBC Driver treats data type&amp;nbsp;&lt;STRONG&gt;Numeric(without precision) AS&lt;/STRONG&gt;&amp;nbsp;as "default" by default, change it to "varchar" then the NUMERIC will be parsed as STRING(1000). Replicate applies the implicit data type mapping from STRING(1000) to custom precision and scale.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; The parameter name in ODBC file is "&lt;STRONG&gt;D6&lt;/STRONG&gt;", it's values are:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;&lt;FONT face="courier new,courier"&gt;Default : -101&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;FONT face="courier new,courier"&gt;varchar : 12&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;FONT face="courier new,courier"&gt;double&amp;nbsp; : 8&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;FONT face="courier new,courier"&gt;memo&amp;nbsp; &amp;nbsp; : -1&lt;/FONT&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; In ODBC Manager it's:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="john_wang_6-1676298847544.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/100351i365BF708F556B64A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="john_wang_6-1676298847544.png" alt="john_wang_6-1676298847544.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3 id="toc-hId-1962198419"&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A id="hoverCardLink" class="lia-link-navigation lia-product-hover-card-link lia-product-mention lia-tooltip-trigger" href="https://community.qlik.com/t5/c-cyjdu72974/Qlik+Replicate/pd-p/qlikReplicate" target="_blank" rel="noopener"&gt;Qlik Replicate&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;nbsp; all versions&lt;BR /&gt;PostgreSQL&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;all Server versions (psqlODBC 11.00.0000 Release and above)&lt;/P&gt;
&lt;H3 id="toc-hId--993259818"&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Internal Investigation ID(s):&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Support cases, #00069371&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Feature Request &lt;A title="Add precision and scale for Postgresql source endpoint for numeric fields" href="https://ideation.qlik.com/app/#/case/281146" target="_blank" rel="noopener"&gt;Add precision and scale for Postgresql source endpoint for numeric fields&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A id="hoverCardLink" class="lia-link-navigation lia-product-hover-card-link lia-product-mention lia-tooltip-trigger" href="https://community.qlik.com/t5/c-cyjdu72974/Qlik+Replicate/pd-p/qlikReplicate" target="_blank" rel="noopener"&gt;Qlik Replicate&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 08:13:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/ta-p/2037219</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2023-11-07T08:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate - How to keep NUMERIC field precision and scale for PostgreSQL source endpoint</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2134469#M10596</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/115309"&gt;@john_wang&lt;/a&gt;&amp;nbsp; - Great blog. one question - How about the NUMERIC fields having Integer values. Those are appearing as (example: 123.000000). pls advise how to fix it.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Nov 2023 12:28:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2134469#M10596</guid>
      <dc:creator>sravyakolli</dc:creator>
      <dc:date>2023-11-03T12:28:11Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate - How to keep NUMERIC field precision and scale for PostgreSQL source endpoint</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2134473#M10598</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/115309"&gt;@john_wang&lt;/a&gt;&amp;nbsp; - Also how to fix it for Replicate on Linux. looks like above screenshot is for Windows ODBC driver.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Nov 2023 12:34:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2134473#M10598</guid>
      <dc:creator>sravyakolli</dc:creator>
      <dc:date>2023-11-03T12:34:28Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate - How to keep NUMERIC field precision and scale for PostgreSQL source endpoint</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2134524#M10599</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/207456"&gt;@sravyakolli&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thank you for the update.&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://community.qlik.com/t5/user/viewprofilepage/user-id/115309" target="_blank"&gt;@john_wang&lt;/A&gt;&amp;nbsp; - Great blog. one question - How about the NUMERIC fields having Integer values. Those are appearing as (example: 123.000000). pls advise how to fix it.&lt;/SPAN&gt;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;If I understood correctly, you could change the data type in the above step (6),&amp;nbsp;&lt;SPAN&gt;from&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;STRING(1000)&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;to&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;INT&lt;/STRONG&gt;, eg INT4.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;A href="https://community.qlik.com/t5/user/viewprofilepage/user-id/115309" target="_blank"&gt;@john_wang&lt;/A&gt;&amp;nbsp; - Also how to fix it for Replicate on Linux. looks like above screenshot is for Windows ODBC driver.&lt;/SPAN&gt;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;The Windows ODBC Manager was used to show the parameter name and parameter values meaning.&lt;/P&gt;
&lt;P&gt;The resolution is same while Replicate running on Linux:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Open&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;PostgreSQL source endpoint&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Go to the&amp;nbsp;&lt;STRONG&gt;Advanced&lt;/STRONG&gt;&amp;nbsp;tab&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Open&amp;nbsp;&lt;STRONG&gt;Internal Parameters&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Add a&lt;EM class="Highlight"&gt;&lt;EM class="Highlight ht3ec7d61a-4558-4809-bebc-3c5e0889f80a"&gt;&amp;nbsp;new&amp;nbsp;&lt;/EM&gt;&lt;/EM&gt;parameter named&amp;nbsp;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;additionalConnectionProperties&lt;BR /&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;Press&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&amp;lt;Enter&amp;gt;&lt;/STRONG&gt;&amp;nbsp;and set the parameter's value to:&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;FONT face="courier new,courier"&gt;D6=12;&lt;BR /&gt;&lt;/FONT&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Let me know if you need any additional assistance.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;John.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Nov 2023 14:53:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2134524#M10599</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2023-11-03T14:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate - How to keep NUMERIC field precision and scale for PostgreSQL source endpoint</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2135226#M10621</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/115309"&gt;@john_wang&lt;/a&gt;&amp;nbsp; - Thanks for your response. We have NUMERIC datatype for most of the tables and they have mix of data. Here is the expected translation. Please let me know how can we achieve this? having to go through each field would be tedious.&lt;/P&gt;
&lt;P&gt;123&amp;nbsp; -&amp;gt; 123&lt;/P&gt;
&lt;P&gt;123.2 - &amp;gt; 123.2&lt;/P&gt;
&lt;P&gt;123.653 - &amp;gt;&amp;nbsp;123.653&lt;/P&gt;
&lt;P&gt;123.4567242424242 - &amp;gt;&amp;nbsp;123.4567242424242&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 06:41:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2135226#M10621</guid>
      <dc:creator>SK2</dc:creator>
      <dc:date>2023-11-07T06:41:04Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate - How to keep NUMERIC field precision and scale for PostgreSQL source endpoint</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2135269#M10624</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/252876"&gt;@SK2&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To make certain that your question has the right reach (our community as well as our active agents), please post your query in our&amp;nbsp;&lt;STRONG&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Replicate/bd-p/qlik-replicate-discussions" target="_blank" rel="noopener"&gt;Qlik Replicate&lt;/A&gt;&amp;nbsp;&lt;/STRONG&gt;forum.&lt;/P&gt;
&lt;P&gt;All the best,&lt;BR /&gt;Sonja&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 08:05:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-How-to-keep-NUMERIC-field-precision-and-scale-for/tac-p/2135269#M10624</guid>
      <dc:creator>Sonja_Bauernfeind</dc:creator>
      <dc:date>2023-11-07T08:05:54Z</dc:date>
    </item>
  </channel>
</rss>

