POST
|
Good idea @JohannesLindner but unfortunately I am still receiving the "Invalid DateTime" in the smart form. I made an edit to my initial post adding in that the layer is from a published feature service in SDE...not sure if that is an issue here or not.
... View more
02-07-2023
07:31 AM
|
0
|
0
|
405
|
POST
|
I have a Survey Date attribute in feature layer that I have set to populate with calculated expression in the smart form. When you open the form to edit the point (not create a new point), the date field is updated to the current date since the calculated expression is now(). Is there a way to not trigger the calculated expression if the field is already populated? When I try to only update if the survey date field is null, I receive an Invalid DateTime error in the form. //Arcade snip for calculating new date if the survey date field is empty if (IsEmpty($feature.SurveyDate)) { return now() } else { return $feature.SurveyDate } result EDIT: This layer is from a feature service published from a SDE database. The survey date field is a Date type field.
... View more
02-06-2023
07:23 PM
|
0
|
2
|
471
|
IDEA
|
@MargaretCrawford I do understand you could use the Identity, Identify, Union, and a number of other tools in conjunction with the Spatial Join to identify which areas do not overlap. I am more looking for the Spatial Join to use an Identify rather than intersect when using the Merge Rule - Join. Below you can see where boxes B and C fall outside of the number boxes. It would be useful to know that they fall out of a spatial join as well. Many situations popup (wetland mapping, biological habitat, survey tracking...) where a "No Value" or "None" is just as important as the intersected areas. For the spatial join it would be useful to include None for example in the image below for box B the join result would be 5,6,None and the result for box C would just be None. I mainly bring this up since I just found the Merge Type - Join and use it a lot. The Identify option is just something we use a lot and looking to streamline a few of our tools.
... View more
01-09-2023
08:10 AM
|
0
|
0
|
507
|
POST
|
Good call....the functionality is totally lost from Pro 3 but still remains in ArcMap 10.8.2.
... View more
11-07-2022
11:29 AM
|
0
|
0
|
732
|
IDEA
|
The ability to use the Join in the Spatial Join tool for the fields is awesome. It currently has the ability to intersect underlying data and return multiple features intersected in 1 attribute. It would be a great benefit if there was an option for using an Identity rather that the intersect option for see where non-intersecting areas exist. In the screenshot below it is nice to see what features the tan shape intersects the pink, but it is sometimes required to see where the tan feature is not intersecting anything.
... View more
11-07-2022
07:39 AM
|
1
|
2
|
640
|
POST
|
@Anonymous User do you know if there are plans to add this functionality in? As of now the GetUser() is still not working in offline mode.
... View more
09-12-2022
01:58 PM
|
0
|
0
|
1064
|
POST
|
I am having an issue calculating fields in ArcGIS Pro and overwriting previously selected data, not the currently selected data. I am using ArcGIS Pro 2.8.3. The feature class I am trying to edit is stored locally. There below steps are taken from another question (Solved: Re: 2.6.1 - field calculator with selection, dange... - Page 2 - Esri Community) by @danbecker and covers my issue exactly, the previous post says solved, but I did not see a solution, just an explanation. Select a record in attribute table. Right click on field, calculate field, specify a string to calculate, hit APPLY make sure and leave the field calculator floating window open change the selection in the table to a different record the field calculator window is already open, don't change anything except a new string to calculate, hit APPLY or OK, doesn't matter Notice what happens…you would expect that the record selected in step #3 would be calculated, i.e. the one currently selected, but it actually calculates the formally selected record, i.e. the selection in step #1. Any idea if there is a correction for this??
... View more
11-10-2021
08:18 AM
|
2
|
5
|
547
|
POST
|
Following....we have the same issue. When we click on a filtered point, we get the popup for all feature at that location. Like Bradly, this was not an issue before the updates this week.
... View more
04-15-2021
02:39 PM
|
1
|
0
|
2973
|
POST
|
I have a custom Arcade expression being used in a web map for a pop-up and it works fine. When this web map is added to a Dashboard, the expression is only partially recognized. I have a "TextFormatting.NewLine" that is not being recognized. Is there a way to have a return carriage in a Dashboard?
... View more
12-17-2020
03:20 PM
|
0
|
1
|
336
|
POST
|
I have a Survey123 that contains multiple surveys spanned across multiple dates and would like to show only the most recent data. This survey includes a repeat of photos, as a point feature class, which might contain 30 points. I have tried to edit the layer definition using the guidance in THIS POST but it only returns the last photo for a given report by date ...not all the points collected on the same date. Is there a topFilter or other definition I could update to show these (using a datetime field)?? This is how the points look for a given survey site-- I would like to show only the red dots in the web map--
... View more
10-08-2020
09:26 AM
|
0
|
0
|
307
|
POST
|
I was able to fix this problem by removing the HTML tags from the choices tab in the XLSForm and republishing using Survey123 3.10. It appears my issue with the white font in the Survey123 App is no longer an issue in 3.10 and republishing removed the tags from the feature reports.
... View more
08-25-2020
08:03 AM
|
0
|
0
|
751
|
POST
|
Thanks for reaching out. I have emailed you my form and template. One thing to note is that I created this in Connect 3.9.x and I was having an issue making the select_one choice labels have white font in the Survey123 App. My work around was to place html tags around the label on the choice tab of the XLSFrom. I believe this might be the root of the issue. The tag does not remain in an exported FGDB of the data nor do I see it in the value of the attribute table but it is expressed in in the form export and on the Survey123 website.
... View more
08-25-2020
07:03 AM
|
0
|
0
|
751
|
POST
|
I am exporting a feature report from Survey123 and the font tag is printing in the report. This survey does use white font in the survey with a black background but I do not see the tag in the attribute table. I am pulling the photo from a related (repeat) table and I am also pulling 3 other attribute values from the main layer, Wetland_Monitoring_v101. Is there something wrong with how I am pulling the attributes from the repeat table or is there a way to have white font in the app but not on the Survey123 website? Screen shot of the tag in the report. The tag is only around the text being pulled from the repeat table, not the main layer. Screen shot of the Word.doc text for the report. Screen shots of data in Survey123. The font here is white.
... View more
08-23-2020
09:27 PM
|
0
|
3
|
804
|
POST
|
Thanks Ruth...I will give this a try and let you know how it works out.
... View more
08-23-2020
09:10 PM
|
0
|
0
|
1168
|
Title | Kudos | Posted |
---|---|---|
1 | 11-07-2022 07:39 AM | |
1 | 04-15-2021 02:39 PM | |
2 | 11-10-2021 08:18 AM | |
2 | 08-04-2020 08:36 AM |
Online Status |
Offline
|
Date Last Visited |
12-06-2023
11:05 PM
|