<?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 Field Maps Tasks: Shift-based (06:00–06:00) filtering using esritask_duedate in ArcGIS Field Maps Questions</title>
    <link>https://community.esri.com/t5/arcgis-field-maps-questions/field-maps-tasks-shift-based-06-00-06-00-filtering/m-p/1688272#M12401</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I’m working with &lt;STRONG&gt;&lt;STRONG&gt;Tasks in ArcGIS Field Maps &lt;/STRONG&gt;&lt;/STRONG&gt;and I’m trying to implement a&amp;nbsp;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;shift-based time filter.&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;DIV&gt;&lt;H3&gt;&lt;U&gt;Goal / Requirement&lt;/U&gt;&lt;/H3&gt;&lt;P&gt;We run operational shifts from &lt;STRONG&gt;06:00 today to 06:00 the next day. &lt;/STRONG&gt;We need the task list to be&amp;nbsp;&lt;STRONG&gt;&lt;STRONG&gt;consistent across midnight, e.g.:&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;A user logs in at 23:00 and sees the tasks for the current shift (06:00 → 06:00).&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The same user logs in again at 02:00 (after midnight) and should still see the same shift tasks, not a new set.&lt;/P&gt;&lt;P&gt;The task layer contains the standard due date field &lt;STRONG&gt;esritask_duedate&lt;/STRONG&gt;, which is filled and used as the “deadline”.&lt;/P&gt;&lt;DIV&gt;&lt;H3&gt;&lt;U&gt;What works (but not sufficient)&lt;/U&gt;&lt;/H3&gt;&lt;P&gt;A basic filter like the following is valid and works logically for “calendar day”, but it &lt;STRONG&gt;breaks after midnight &lt;/STRONG&gt;because the day changes:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;SPAN&gt;esritask_duedate BETWEEN (CURRENT_DATE + 0.2083333333) AND (CURRENT_DATE + 1.2083333333)&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;P&gt;&lt;EM&gt;(0.2083333333 = 5/24, intended to represent “06:00 local” depending on time zone setup.)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;U&gt;&lt;STRONG&gt;Problem:&lt;/STRONG&gt;&lt;/U&gt;&lt;/EM&gt; when the calendar day changes at midnight, users logging in between 00:00–06:00 see the next day’s window, and tasks from the ongoing shift are no longer included.&lt;/P&gt;&lt;DIV&gt;&lt;H3&gt;&lt;U&gt;Attempted solution (dynamic switch “before/after 06:00”)&lt;/U&gt;&lt;/H3&gt;&lt;P&gt;To keep the same shift across midnight, I tried a dynamic “switch” logic:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If current time is &lt;STRONG&gt;before 06:00, filter &lt;STRONG&gt;yesterday 06:00 → today 06:00&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;Else filter &lt;STRONG&gt;today 06:00 → tomorrow 06:00&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp; (CURRENT_TIMESTAMP &amp;lt;&amp;nbsp; (CURRENT_DATE + 0.2083333333) AND&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; esritask_duedate BETWEEN ((CURRENT_DATE - 1) + 0.2083333333) AND (CURRENT_DATE + 0.2083333333))&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp; OR&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp; (CURRENT_TIMESTAMP &amp;gt;= (CURRENT_DATE + 0.2083333333) AND&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; esritask_duedate BETWEEN (CURRENT_DATE + 0.2083333333) AND (CURRENT_DATE + 1.2083333333))&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV&gt;&lt;H3&gt;&lt;U&gt;Issue&lt;/U&gt;&lt;/H3&gt;&lt;P&gt;This expression appears &lt;STRONG&gt;valid in Field Maps Designer, &lt;/STRONG&gt;but when opening the map in the&lt;STRONG&gt;&lt;STRONG&gt;Field Maps mobile app, &lt;/STRONG&gt;&lt;/STRONG&gt;Tasks fail to load and the app shows:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;“Tasks couldn’t be loaded. Contact the map author for more information.”&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I also tested using EXTRACT(HOUR FROM CURRENT_TIMESTAMP) earlier, but Field Maps mobile did not support it either (same outcome).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;U&gt;&lt;FONT size="5"&gt;Question&lt;/FONT&gt;&lt;/U&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;Is there a Field Maps mobile limitation &lt;/STRONG&gt;regarding dynamic SQL functions (CURRENT_TIMESTAMP, EXTRACT, etc.) in&amp;nbsp;&lt;STRONG&gt;&lt;STRONG&gt;Tasks filters / to-do lists?&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;Is there a &lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;recommended approach &lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;to implement a &lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;06:00–06:00 shift window &lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;using only esritask_duedate that works reliably in Field Maps mobile?&lt;/LI&gt;&lt;LI&gt;If this is not supported via SQL in Field Maps mobile, what is the&amp;nbsp;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;best practice workaround?&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;e.g., precomputing a shift anchor field (like shift_date) on insert/update (server-side or via automation), and filtering on that instead?&lt;/LI&gt;&lt;/OL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any hints, confirmed limitations, or working examples would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 04 Mar 2026 08:21:09 GMT</pubDate>
    <dc:creator>ZentraleTechnik</dc:creator>
    <dc:date>2026-03-04T08:21:09Z</dc:date>
    <item>
      <title>Field Maps Tasks: Shift-based (06:00–06:00) filtering using esritask_duedate</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-questions/field-maps-tasks-shift-based-06-00-06-00-filtering/m-p/1688272#M12401</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I’m working with &lt;STRONG&gt;&lt;STRONG&gt;Tasks in ArcGIS Field Maps &lt;/STRONG&gt;&lt;/STRONG&gt;and I’m trying to implement a&amp;nbsp;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;shift-based time filter.&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;DIV&gt;&lt;H3&gt;&lt;U&gt;Goal / Requirement&lt;/U&gt;&lt;/H3&gt;&lt;P&gt;We run operational shifts from &lt;STRONG&gt;06:00 today to 06:00 the next day. &lt;/STRONG&gt;We need the task list to be&amp;nbsp;&lt;STRONG&gt;&lt;STRONG&gt;consistent across midnight, e.g.:&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;A user logs in at 23:00 and sees the tasks for the current shift (06:00 → 06:00).&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The same user logs in again at 02:00 (after midnight) and should still see the same shift tasks, not a new set.&lt;/P&gt;&lt;P&gt;The task layer contains the standard due date field &lt;STRONG&gt;esritask_duedate&lt;/STRONG&gt;, which is filled and used as the “deadline”.&lt;/P&gt;&lt;DIV&gt;&lt;H3&gt;&lt;U&gt;What works (but not sufficient)&lt;/U&gt;&lt;/H3&gt;&lt;P&gt;A basic filter like the following is valid and works logically for “calendar day”, but it &lt;STRONG&gt;breaks after midnight &lt;/STRONG&gt;because the day changes:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;SPAN&gt;esritask_duedate BETWEEN (CURRENT_DATE + 0.2083333333) AND (CURRENT_DATE + 1.2083333333)&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;P&gt;&lt;EM&gt;(0.2083333333 = 5/24, intended to represent “06:00 local” depending on time zone setup.)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;U&gt;&lt;STRONG&gt;Problem:&lt;/STRONG&gt;&lt;/U&gt;&lt;/EM&gt; when the calendar day changes at midnight, users logging in between 00:00–06:00 see the next day’s window, and tasks from the ongoing shift are no longer included.&lt;/P&gt;&lt;DIV&gt;&lt;H3&gt;&lt;U&gt;Attempted solution (dynamic switch “before/after 06:00”)&lt;/U&gt;&lt;/H3&gt;&lt;P&gt;To keep the same shift across midnight, I tried a dynamic “switch” logic:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If current time is &lt;STRONG&gt;before 06:00, filter &lt;STRONG&gt;yesterday 06:00 → today 06:00&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;Else filter &lt;STRONG&gt;today 06:00 → tomorrow 06:00&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp; (CURRENT_TIMESTAMP &amp;lt;&amp;nbsp; (CURRENT_DATE + 0.2083333333) AND&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; esritask_duedate BETWEEN ((CURRENT_DATE - 1) + 0.2083333333) AND (CURRENT_DATE + 0.2083333333))&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp; OR&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp; (CURRENT_TIMESTAMP &amp;gt;= (CURRENT_DATE + 0.2083333333) AND&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; esritask_duedate BETWEEN (CURRENT_DATE + 0.2083333333) AND (CURRENT_DATE + 1.2083333333))&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV&gt;&lt;H3&gt;&lt;U&gt;Issue&lt;/U&gt;&lt;/H3&gt;&lt;P&gt;This expression appears &lt;STRONG&gt;valid in Field Maps Designer, &lt;/STRONG&gt;but when opening the map in the&lt;STRONG&gt;&lt;STRONG&gt;Field Maps mobile app, &lt;/STRONG&gt;&lt;/STRONG&gt;Tasks fail to load and the app shows:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;“Tasks couldn’t be loaded. Contact the map author for more information.”&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I also tested using EXTRACT(HOUR FROM CURRENT_TIMESTAMP) earlier, but Field Maps mobile did not support it either (same outcome).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;U&gt;&lt;FONT size="5"&gt;Question&lt;/FONT&gt;&lt;/U&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;Is there a Field Maps mobile limitation &lt;/STRONG&gt;regarding dynamic SQL functions (CURRENT_TIMESTAMP, EXTRACT, etc.) in&amp;nbsp;&lt;STRONG&gt;&lt;STRONG&gt;Tasks filters / to-do lists?&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;Is there a &lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;recommended approach &lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;to implement a &lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;06:00–06:00 shift window &lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;using only esritask_duedate that works reliably in Field Maps mobile?&lt;/LI&gt;&lt;LI&gt;If this is not supported via SQL in Field Maps mobile, what is the&amp;nbsp;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;best practice workaround?&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;e.g., precomputing a shift anchor field (like shift_date) on insert/update (server-side or via automation), and filtering on that instead?&lt;/LI&gt;&lt;/OL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any hints, confirmed limitations, or working examples would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 04 Mar 2026 08:21:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-questions/field-maps-tasks-shift-based-06-00-06-00-filtering/m-p/1688272#M12401</guid>
      <dc:creator>ZentraleTechnik</dc:creator>
      <dc:date>2026-03-04T08:21:09Z</dc:date>
    </item>
    <item>
      <title>Re: Field Maps Tasks: Shift-based (06:00–06:00) filtering using esritask_duedate</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-questions/field-maps-tasks-shift-based-06-00-06-00-filtering/m-p/1688826#M12430</link>
      <description>&lt;DIV&gt;I’m facing the exact same issues, but only in Field Maps. I’m currently limited by the available date-filtering (temporal filtering) functions—similar to what QFIELD supports (see link above). I can’t create a date filter that returns &lt;EM&gt;only the previous shift&lt;/EM&gt;, which would allow my operators to filter and review what was completed during the prior shift.&lt;BR /&gt;&lt;BR /&gt;&lt;A title="https://docs.qfield.org/how-to/advanced-how-tos/temporal-filtering/" href="https://docs.qfield.org/how-to/advanced-how-tos/temporal-filtering/" target="_blank" rel="noopener"&gt;https://docs.qfield.org/how-to/advanced-how-tos/temporal-filtering/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;I’ll keep an eye on what people post here as a solution.&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 05 Mar 2026 22:00:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-questions/field-maps-tasks-shift-based-06-00-06-00-filtering/m-p/1688826#M12430</guid>
      <dc:creator>LaurentSavoy1</dc:creator>
      <dc:date>2026-03-05T22:00:39Z</dc:date>
    </item>
    <item>
      <title>Re: Field Maps Tasks: Shift-based (06:00–06:00) filtering using esritask_duedate</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-questions/field-maps-tasks-shift-based-06-00-06-00-filtering/m-p/1689630#M12449</link>
      <description>&lt;P&gt;When testing this, i found out that Date Arithmetic is not supported on the Client although the expression seems to be valid in FieldMaps Designer.&lt;BR /&gt;I tested expressions such as&amp;nbsp;CURRENT_DATE + 1 = CURRENT_DATE + 1 which compared to 1=1 delivers no results.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Mar 2026 12:20:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-questions/field-maps-tasks-shift-based-06-00-06-00-filtering/m-p/1689630#M12449</guid>
      <dc:creator>MarcMuehleisen89</dc:creator>
      <dc:date>2026-03-10T12:20:54Z</dc:date>
    </item>
  </channel>
</rss>

