Latest Contributions by CalenDaugherty

I am glad somebody else noticed this. I too see this small lag in the new viewer vs the old. Granted, it is usually only a second or 2, but why is this slower than the old viewer? Why should the new more advanced viewer be slower for a straightforward function, not some edge case? I don't have extensive programming knowledge, but maybe this is related to the Javascript API v4 being more dependent on the systems graphics card? Would love to hear feedback from ESRI on whether they are aware of this issue. ... View more

I'll upvote this, but frankly "Ideas" should be reserved for new ideas / enhancements, not asking for functionality that was in older versions but is missing in newer ones. It is disappointing the new map viewer has been out for years and related records are not available. I think ESRI is really leaving users hung out to dry on this one. ... View more

This page has a pretty good summary of the retired/modified workflows from 10.9.1 to 11 https://enterprise.arcgis.com/en/get-started/latest/windows/considerations-for-upgrades-to-11-0-and-later.htm#ESRI_SECTION2_37DA14A1DB684A23A5F64A77ED41EBCF   ... View more

I posted here around a year ago, citing a ESRI road map that indicated related records would be in the new map viewer in “Early 2022”. Obviously that time has come and gone. I though it was finally here with the update from a few weeks ago, but as others have indicated, this update is for hosted layers only. Would love to hear some answers from ESRI as to the when related records coming from an Enterprise GDB can be used in the new mapviewer and new apps. Are related records in an Enterprise GDB going away? If so, I think GIS users need to know so they can plan appropriately. Related records in hosted features are pretty limited at the moment. It frustrating to try and stay up to date with the latest versions of apps when seemingly basic functionality like this is left out.  To me, related records are a pretty core functionality. If ESRI wants users to embrace their vision of “next generation” GIS, then they should either migrate core functionalities or provide a roadmap of how existing workflows should be replaced. ... View more

Hi, I believe related record functionality is not yet available in the new map viewer. https://doc.arcgis.com/en/arcgis-online/reference/faq.htm#ESRI_QUESTIONANSWER_B6637795FB5F4953B40842F64C80D90D If you scroll down to the section "What Map Viewer Should I Use", it indicates the related records functionality is not in the new map viewer. This was on an ESRI road map for early 2022 . . . I would anticipate that it will become available in a future update of ArcGIS Online. ... View more

Thanks for the reply. In reviewing some of the instances where I have encountered this behavior, I have noticed something similar to what you describe . . . many .gdbtable files that don't seem to be removed during Compact. If the database size has grown and there is a single large .gdbtable, Compact seems to work well in shrinking it. But it does not seem to get rid of the "extra" .gdbtable files. Copying the data to a new geodatabase seems to only bring along the needed files, so it effectively reduces to size of the data. This issue does not always occur, so I have still have not isolated the scenarios that would cause it. ... View more

Thanks for the reply. The compact does work in some instances. It seems like when I try to use it with a fgdb that is a data source for a map service, there are issues. I know the map service must be stopped for compact to run . . . the compact will run successfully, but it almost as if even though the map service is stopped, something is still preventing compact from getting rid off all the bloated tables. I would have to do some more testing to pinpoint an exact scenario. ... View more

Just wanted to chime in on my experience with this issue. Whenever I use a tools like Delete Features - Append, the file geodatabase bloats up in size. If I am running a Python script every night doing something like this, then the size can grow quickly. A fgdb that started as 20MB can grow to a GB or more. I don't notice much of a performance issue in ArcMap or ArcGIS Pro, but scripts running against the data can take progressively longer. Compact will shrink the fgdb by a bit, but not by much. It is the xxxx.gdbtable file size that grows . . . its like orphaned data is left behind each time. The only way I have been able to do repetitive processes without this occursing is to include a step to completely delete the features class, and then bring in the data, rather than doing delete features - append. I would be interested to hear if anyone has come across a solution to help with this. ... View more

I have had this exact same problem. I can't pinpoint what exactly causes it (am thinking it is losing connection when saving an edit, but nothing happens where I am sure that is the cuase), but I experience what all the other users said (differing total number of features, error thrown when sorting, not all features drawing). Compress, compact, nothing I tried worked. A workaround I have found similar to some other users is to bring the data into QGIS. If you look at the attribute table it will say, for example, 720 features, 716 filtered. If you export to shapefile, you will end up with 716 features, with the corrupt records removed. You can then either create a new fgdb feature class in your schema, and append the shapefiles back in (being mindful of the truncated field names not mapping automatically), or if you have a unique ID, do some sort of join to get your features back. While I understand any data can get corrupted, I concur with others that I haven't seen this behavior in SDE or shapefiles, so I feel like there is the potential for some sort of fix or recovery tool in the ESRI environment, or at least some sort of tool that would tell you what the error was. ... View more

I ran into this same issue. I found a semi work-around . . . . If you split the start date / end date query with another type of query, they seem to both show up. If the start date / end date queries are consecutive, only start date seems to appear. This worked for me, but I was unable to do a query that was only start date / end date ... View more