nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

QuickCapture- Arcade Expression Issue Calculating "Current Year"- Bug?

Amanda.Huber@threeriversparks.org_trpd

Hello QuickCapture Team,

We're currently working on a project where we're trying to calculate the current year into our field when a button is pushed using Arcade Expressions.

We have tested numerous ways of writing the expression and all return an empty result even though the Arcade expression editor shows the return to be correct.

We have tried to return this as both a Number() and Text() to two respective small int and text fields with no luck.

When testing in AGOL popups, our expressions work with no issues. Leading us to believe this may be an arcade version support issue.

Expressions we've tried:

(This last one actually wouldn't allow the QuickCapture app to submit the record)

Please let us know if this is a Bug, Arcade version issue, or something else.

Thanks,

Amanda Huber

Find more posts tagged with

ArcGIS QuickCapture Mobile App

ArcGIS QuickCapture Designer

Accepted answers

JHasthorpe

@Amanda__Huber - There was a bug in the mobile application. In the december release (1.21) we will have a fix for Text(Year(Now())) not returning a string version of the date.

This will resolve the issue that you were seeing.

All comments

Amanda.Huber@threeriversparks.org_trpd

@JohnathanHasthorpe is there any update on when DateOnly() be supported by the QuickCapture mobile app?

Amanda.Huber@threeriversparks.org_trpd

@JohnathanHasthorpe when will DateOnly() be supported by the QuickCapture mobile app? Is there an estimated timeline for this?

Our text field for date is a great workaround but not ideal for using other products like webmap and pipeline filters.

Thanks,

Amanda

JHasthorpe

@Amanda__Huber - There was a bug in the mobile application. In the december release (1.21) we will have a fix for Text(Year(Now())) not returning a string version of the date.

This will resolve the issue that you were seeing.

ChristopherCounsell

https://developers.arcgis.com/arcade/function-reference/date_functions/#dateonly

The function DateOnly() is since version 1.24 and QuickCapture states it's on 1.18. So it would be both the fields and the function.

Amanda.Huber@threeriversparks.org_trpd

Hi @chrichris ,

Thanks for the response! To clarify, the documentation for Arcade Expressions in QuickCapture refers to DateOnly Fields not the DateOnly() function. That being said I now understand where you're seeing these version differences, sounds like the documentation is what is confusing.

It's still not clear why Date() and Year(Now()) are causing issues when submitting the record.

Other expressions in the project are working fine and no issues which leads us to thinking it's just a QuickCapture issue with dates.

We've opened an Esri support case already and plan to troubleshoot with them further.

Thanks,

Amanda Huber

ChristopherCounsell

Re reading the post it appears you're having issues with any calculation methods. Suggest trying with a new blank project (so it's easily reproducible) and reaching out to tech support if you haven't already.

ChristopherCounsell

DateOnly() is supported in Arcade 1.24 onward.

https://developers.arcgis.com/arcade/function-reference/date_functions/#year

QuickCapture uses 1.18

https://doc.arcgis.com/en/quickcapture/help/arcade-expressions.htm

Do not expect Arcade to work universally across the platform. That may be the goal but newer stuff we use in core profiles like map popups takes longer to reach other parts of the platform.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.