Latest Contributions by ZacharyHart

so does 'base table' represent the default version of the GDB? The versions are post & reconciled to the default version daily and and compression is run weekly. If I query say the top 10 records sorted by 'last_edited_date' descending, i'm seeing stuff from 2019 which would be the inception of this particular GDB. ... View more

thanks so much! This is a great write-up! ... View more

I'm intrigued if you are willing to share more. ... View more

This makes good sense, thank you! ... View more

Is there anyone from Esri willing to answer this? We have a number of GP tools we'd like to roll out to our users that are currently working in Pro using FS within the code but cannot be successfully published. Why wouldn't you want to leverage the speed of FS in your code vs direct GDB connections? ... View more

Is there anyone from Esri willing to answer this? ... View more

It's really too bad the group filter won't work for tables ... View more

@KalenMyers  BTW, this seems to be related to this idea here: https://community.esri.com/t5/arcgis-web-appbuilder-ideas/display-nested-relates-in-web-app-builder/idi-p/938150 ... View more

@GarethBaker1  Did you ever get to the bottom of this? We have a Federated Enterprise site, single machine/site though, but we are now noticing odd behavior with feature service based editing and editor tracking...erroneous user names. We've been using editor tracking for years and have not noticed this. We are recently upgraded from 10.7 to 10.9.1 FWIW. ... View more

I'll echo everyone else's comments here. How has this not been implemented yet!? This is very difficult to explain to users and especially problematic with cascading relationships. [Note that this problem does not exist at all in Pro.] For example, let's say we have 3 related tables in descending parent-to-child 1:M relationships. If you apply a filter to table 2, and then 'show related records', Table 2 returns the correct related records. However, if you then 'show related records' in Table 2 without applying a filter to Table 2, the tool will time out in attempting to poll all records in Table 2 for relationships with Table 3. Server Manager will then trigger an warning in server logs: for Max Record Count and will actually trigger warnings amounting for whatever is set in the service properties 'Maximum Number of Records Returned by Server'. So if your service has the default of 1000 records, you will have 1,000 warnings in your server logs! This is ridiculous... Actual warning message shown below: MaxRecordCount limit reached; ignoring any remaining objects in the query result for Table: Table 3. ... View more

I'm unfortunately still not having any luck with this. ... View more

Unfortunately, this doesn't seem to trick the validation process:   ... View more