<?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 Write Console Statements to the Field Maps Log in ArcGIS Field Maps Ideas</title>
    <link>https://community.esri.com/t5/arcgis-field-maps-ideas/write-console-statements-to-the-field-maps-log/idi-p/1172218</link>
    <description>&lt;P&gt;When creating an arcade expression for ArcGIS Field Maps Forms we can print to the console in the arcade editor to help develop our expressions.&amp;nbsp; When editing data in the form in the web map viewer in a browser we can see the our consoled messages in dev tools to help troubleshoot.&lt;/P&gt;&lt;P&gt;Please consider writing these messages to the ArcGIS Field maps log.&amp;nbsp; I would be content with just writing the Form-Calculation Profile messages to the FM log (valueExpressions), but it might also be useful to write the Constraint Profile messages (editableExpression, visibleExpression, requiredExpression) as well for troubleshooting purposes.&lt;/P&gt;&lt;P&gt;These might flood the log, but we can always comment out our console statements in the arcade expression for production. Or, another idea, might be to add a &lt;U&gt;verbose&lt;/U&gt;&amp;nbsp;option in Field Maps that would then and only then enable writing the console statements to the log.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Justin&lt;/P&gt;</description>
    <pubDate>Mon, 09 May 2022 22:28:31 GMT</pubDate>
    <dc:creator>JustinReynolds</dc:creator>
    <dc:date>2022-05-09T22:28:31Z</dc:date>
    <item>
      <title>Write Console Statements to the Field Maps Log</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-ideas/write-console-statements-to-the-field-maps-log/idi-p/1172218</link>
      <description>&lt;P&gt;When creating an arcade expression for ArcGIS Field Maps Forms we can print to the console in the arcade editor to help develop our expressions.&amp;nbsp; When editing data in the form in the web map viewer in a browser we can see the our consoled messages in dev tools to help troubleshoot.&lt;/P&gt;&lt;P&gt;Please consider writing these messages to the ArcGIS Field maps log.&amp;nbsp; I would be content with just writing the Form-Calculation Profile messages to the FM log (valueExpressions), but it might also be useful to write the Constraint Profile messages (editableExpression, visibleExpression, requiredExpression) as well for troubleshooting purposes.&lt;/P&gt;&lt;P&gt;These might flood the log, but we can always comment out our console statements in the arcade expression for production. Or, another idea, might be to add a &lt;U&gt;verbose&lt;/U&gt;&amp;nbsp;option in Field Maps that would then and only then enable writing the console statements to the log.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Justin&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 22:28:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-ideas/write-console-statements-to-the-field-maps-log/idi-p/1172218</guid>
      <dc:creator>JustinReynolds</dc:creator>
      <dc:date>2022-05-09T22:28:31Z</dc:date>
    </item>
    <item>
      <title>Re: Write Console Statements to the Field Maps Log</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-ideas/write-console-statements-to-the-field-maps-log/idc-p/1270435#M1126</link>
      <description>&lt;P&gt;would save much time when searching for none syntactic errors (logical errors) and to log feature values etc.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Mar 2023 15:09:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-ideas/write-console-statements-to-the-field-maps-log/idc-p/1270435#M1126</guid>
      <dc:creator>schenardi</dc:creator>
      <dc:date>2023-03-22T15:09:07Z</dc:date>
    </item>
  </channel>
</rss>

