<?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>idea Python Value Table Improvements in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/python-value-table-improvements/idi-p/933067</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;At 10.1, python toolboxes were introduced and included the ability to have multi-column value table parameters. However, they lack the ability to do&amp;nbsp;useful things such as drive the values in a column of type Field based on the selection in a column of type Feature Layer, or pick the&amp;nbsp;values for a column of type String&amp;nbsp;from a coded value domain.&lt;BR /&gt;&lt;BR /&gt;I hereby vote to make the python geoprocessing tool multi-column value table parameters full fledged, as can be programmed in a dll gp tool. This should be done&amp;nbsp;both&amp;nbsp;in python toolboxes and in regular python tools (by adding value table, and a sub-dialog to define them,&amp;nbsp;to the parameter types that can be defined via a python tool's properties).&lt;BR /&gt;&lt;BR /&gt;Thanks in advance...

&lt;!-- content transformation source ID: 087E00000004RYs --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 31 Dec 2012 00:01:28 GMT</pubDate>
    <dc:creator>RandalGreene1</dc:creator>
    <dc:date>2012-12-31T00:01:28Z</dc:date>
    <item>
      <title>Python Value Table Improvements</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/python-value-table-improvements/idi-p/933067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;At 10.1, python toolboxes were introduced and included the ability to have multi-column value table parameters. However, they lack the ability to do&amp;nbsp;useful things such as drive the values in a column of type Field based on the selection in a column of type Feature Layer, or pick the&amp;nbsp;values for a column of type String&amp;nbsp;from a coded value domain.&lt;BR /&gt;&lt;BR /&gt;I hereby vote to make the python geoprocessing tool multi-column value table parameters full fledged, as can be programmed in a dll gp tool. This should be done&amp;nbsp;both&amp;nbsp;in python toolboxes and in regular python tools (by adding value table, and a sub-dialog to define them,&amp;nbsp;to the parameter types that can be defined via a python tool's properties).&lt;BR /&gt;&lt;BR /&gt;Thanks in advance...

&lt;!-- content transformation source ID: 087E00000004RYs --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2012 00:01:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/python-value-table-improvements/idi-p/933067</guid>
      <dc:creator>RandalGreene1</dc:creator>
      <dc:date>2012-12-31T00:01:28Z</dc:date>
    </item>
  </channel>
</rss>

