Latest Contributions by MikeMinami

Create an expression with this: Proper ($feature.City, 'firstword') Where in my example, I have a field called City. Then you can use that expression like a field in your custom popup. It will also appear in the table. Mike ... View more

From the error message, it appears you're using the extract function. This function, I believe, returns a number. If you are trying to assign this value to a date field, you'll get a field type mismatch of trying to calculate a number into a date field. If your goal is to simply add 180 days to a date in a field and assign it to another field, you can form an expression like this: [PermitDate] + 180 Under normal circumstances, this would yield a new date 180 days into the future. HOWEVER, THERE IS A BUG in AGOL with date addition, where it doesn't work. Subtraction, however works. So try this expression [PermitDate] - -180 Where you subtract negative 180. Mike ... View more

Do you own the layer?  If not, AGOL probably shouldn't be showing you the Edit button. Is the layer being shared in a group with shared access and update? In AGOL, lists (domains) are specific to individual fields. There is no concept currently of shared domains, like Pro has. Mike ... View more

Erica, I don't think Collector would be the issue. What version of Pro are you running? I'm using the latest 2.2.3. Are you querying on a date/time that is recent to the current time? This is a long shot that the time zone is somehow impacting the query. If the values are greater than a day ago, you're probably fine. Are you able to track the request sent from Pro to ArcGIS Online? You can see if the query is working.  Are you able to share your layer so we can try it? Mike ... View more

Alison, Thanks for your feedback. Currently, the visibility of fields in the table is linked to visibility in the popup for the reason I described above. Thus, to make a field visible in the table, it must also be visible in the popup.  I will clarify that the field will only become visible in popups defined as 'a list of field attributes' and not the other popup configuration types. I agree that this is not the best solution to the problem, but it's the best solution we can release in the short term. We have considered other options, but they too are not perfect. We will be continuing to work in this area to improve the experience. If you are concerned about the public viewing field attributes that aren't for public consumption, the best solution is to use a hosted feature layer view. With these layers, you can explicitly set a subset of fields and features the public can see. Thanks, Mike ... View more

Alex,  Are you checking the fields definition of the view layer? The newly added field will not show up automatically in 'configure attributes' from the popup configuration because everyone can see this. You have to define it as a property of the view layer here: Once added, you'll see it when configuring your popup Mike ... View more

Enhancement to make newly added fields visible immediately Pending some ongoing testing, at the next release, newly added fields will immediately be visible in the table. If for some reason our testing fails and we can't release this feature, I'll post here. But, it seems like it should go through. New fields will also appear in popups. How do you make your field 'permanently' visible today before the next release? Currently, if your field is not showing up in the table, you have to make it visible. You do this through the popup configuration. So, on the Visualize tab, configure the popup. Choose the Configure Attributes option to display this dialog box. You will need to check the option to 'Display' the field. Save, and you'll now see your field. In the current release, why are newly added fields sometime visible and sometimes not? It depends if there is a popup defined on the layer already. If there is, and you've customized in in any way, a newly added field will not be visible. At the time, we were being conservative and didn't want to mess up any custom popup you may have configured by adding a new field to it. (With the enhancement, you'll now get it.) There really isn't any relationship to the age of the layer, but I suppose the older a layer is, the more likely that you may have configured the popup or it got configured automatically in some way. Layers published from Desktop might already have a popup defined too.  Why does it work this way now? In the beginning of AGOL, there were only popups, no tables. Then tables were added to the map viewer and it made sense that the fields you see in the table would match what you see in the popup, so the table just displayed the visible fields defined in the popup. I don't think you could even add new fields at this point. Then, the Data tab was introduced, but it still inherited the visible fields defined in the popup. Hope this helps explain things, Mike ... View more

Is the problem specific to this layer? For example, are you able to set a definition query with a date field on a different hosted feature layer? Are you able to use the Filter tool in ArcGIS Online to set up the same query? Mike ... View more

You might want to cross post here. https://community.esri.com/community/gis/analysis  Mike ... View more

Hi Erica, I am not seeing the same behavior. I am able to set a definition query in pro using a date field in my hosted feature layer in ArcGIS Online. I assume you are signed in to pro and are accessing your own content. How is the item shared? Does it draw correctly? Are you able to set a definition using other fields?  Mike ... View more

Can you share your web map? I'm also assuming the services are publicly accessible. Alternatively, you might try opening the web browser developer tools that track network requests. You might get a more informative error message when you look at the request that is failing. Mike ... View more