Latest Contributions by PeterKing

In ArcCatalog, users are able to right click a feature class contained within the Enterprise Database, select Manage > Locks to view who or what is locking the individual Feature.   Now in Pro, users must right-click the database connection in the Catalog pane, click Properties, and expand the Connections section, then click Show connected users and locks. Then users must drill down to find the source of the feature lock via Object Name, Lock Type, or Lock Owner. This process is cumbersome to perform when searching for locks on an individual feature, especially if there are numerous editors and services running within the enterprise. ArcCatalog performs the action quickly and efficiently via the individual feature "Manage" menu.  Often times feature parity is the key to adoption. ... View more

Im sure that this is a basic question so thanks in advance. I currently have an Arcade expression within a Javascript API WebApp that determines if a feature meets a DateDiff expression. The results from the Arcade expression are then sent to a UniqueValueRenderer within the app. var currentExpired = "IIf(DateDiff(Date(),$feature.DATERECEIVED,'days') > 365, 'Expired', 'Current')" I am trying to add a third condition and have written the following (though not truly in Arcade): var currentExpired = (DateDiff(Date(),$feature.DATERECEIVED,'days')) if (currentExpired > '365') { return 'Expired'; } else if (currentExpired < '7') { return 'Upcoming'; } else { return 'Current'; }   I am trying to symbolize features that have a DATERECEIVED greater than 365 as 'Expired', those that are less than 7 days as upcoming, and everything else as current. Unfortunately, the logic seems to be flawed in that the upcoming features being symbolized are those that have been received within the last 7 days. Where have I gone wrong? Also, any ideas on how to write the expression in a truly Arcade format?  ... View more