Latest Contributions by ZacharyHart

Is this expected behavior? ... View more

I'm sure it would be possible, but I'm fortunate to (now days) have IT support to manage our Azure infrastructure. (I don't miss the days of having to be the DBA, server admin, and everything else needed to keep GIS stack of physical servers all up and working while trying to manage an Enterprise system (with project work!) all on top of that!).  Keep me posted on how this next phase goes for you! ... View more

our configuration is a bit different than yours. I presume you are using this article as guidance based on what you've referenced in your original post: https://support.esri.com/en/technical-article/000024588 I'm keying into this part here: Edit the License Manager Info text box. Replace the default Azure machine name with the License Manager host name. If a client is connecting from a different domain than the License Manager, add the FQDN instead of the hostname of the License Manager. Our LM is hosted on the same VM as Enterprise and therefore has the same host name. So we changed nothing here. Additionally, because our Azure Environment is stitched to our domain/network (kinda a WAN) we did not include the FQDN. I believe the URL you provided is what you're referring to as your FQDN of the VM? Do you have anyone as the admin of your Azure environment? I also came across this: https://support.esri.com/en/technical-article/000027816 and this also references items related to your FQDN...again, I don't know all the details about your particular environment. ... View more

I'm not quite sure I understand the host name changes, but they sound problematic. The host name in Portal Admin and our LM is simply the name of the VM...we've never made changes to that. What I can tell you is that if any of our users attempt to use Pro/connect to the LM while off network, they are unable to unless they initiated a VPN connection to our network.  I don't know what IT resources your organization has but this is the time to engage with them. By ping, I mean can you ping the host name of the VM itself? I presume you will not be able to. Are you able to revert your changes to the host name in LM and Portal Admin and then try the connection from your Pro in Azure again? The cloud builder adds in a load balancer by default which adds a layer of complexity here. It also creates your virtual directories in Azure storage. I don't know your use case here, like how large of a deployment you are scoping out. I will also be honest in saying it has been some time since I've worked with cloud builder. All that said, our experience with it was very poor and we spent so much time on the clean-up configuration after the initial deployment. In the end, we ended up scrapping all of it and redeploying conventionally within an Azure VM.   ... View more

Are there any AV applications blocking the process somehow? ... View more

Are you on the same network/domain as your Azure deployment? Does your IT provide you with VPN? Can you ping the host from your desktop/workstation? As an additional test: on your/one of your VM's in Azure, can you install Pro there and test the connection to LM? (I'm presuming you've configured Pro appropriately to connect to Portal etc. in the licensing configuration). ... View more

Should I try somewhere else on Geonet for this? ... View more

@SeanKMcGinnisMy fault...I was thinking of the Survey123 Connector for Enterprise. The ArcGIS Connector for Enterprise will be a welcome addition! ... View more

@tigerwoulds  when i try what you suggest using the sample code from the tutorial I get: AttributeError: 'list' object has no attribute 'services' ... View more

at this time, the ArcGIS Connector for Power Automate only connects to ArcGIS Online. Could you please clarify this? Do you mean the direction of data flow from Power Automate/MS365 to Enterprise is not supported? I ask this because we do have an ArcGIS Enterprise connector which is set to capture basic info from Portal webhooks which feeds into other Power Automate flows. I'm only familiar with one connector for ArcGIS in Power Automate. ... View more

To the first point, what I'm saying is the most recent record in the base table (according to editor tracking) is from 2019-09-18 15:23:13.0 and therefore every other record in that table is older than that. (And would therefore indicate that the base table has never been updated!?) An astute guess! We do indeed have offline replicas in the mix here. Everything is configured according to this Esri doc here. The FS is configured to create a version per user. We have a version of the data to control all the field user/offline versions as described in the article and we would most closely resemble 'Workflow 3' The script responsible for dealing with the versions (using code similar to what is cited in the doc) utilizes the same GP tool you reference. The code builds a list of versions who's parent version is the DB version I mention above and then reconciles them, and then reconciles the controlling version to the default version. Partial code here:     verReconcileList = [] #Create a list of children of the Data Inspector version: for version in versions: if version.parentVersionName == inspectionVersion: verReconcileList.append(version.name) versionName = (version.name.split(".")[1]).split("/")[0] lastModified = version.lastModified print("{0} Last modified: {1}".format(versionName,lastModified)) # Perform maintenance if versions are found, otherwise there is no maintenance to perform. if len(verReconcileList)>0: # Get a list of versions from the database versions = arcpy.da.ListVersions(workspace) # Reconcile user versions to CollectedFieldData version arcpy.ReconcileVersions_management(workspace, "ALL_VERSIONS", inspectionVersion, verReconcileList, "LOCK_ACQUIRED", "NO_ABORT", "BY_OBJECT", "FAVOR_TARGET_VERSION", "POST", "KEEP_VERSION", "c:/temp/reconcilelogCollected.txt") # Reconcile CollectedFieldData version to Default version arcpy.ReconcileVersions_management(workspace, "ALL_VERSIONS", "sde.DEFAULT", inspectionVersion, "LOCK_ACQUIRED", "NO_ABORT", "BY_OBJECT", "FAVOR_TARGET_VERSION", "POST", "KEEP_VERSION", "c:/temp/reconcilelogDefault.txt")       In order to control lag between user syncs and making updates visible to web services and GIS staff, this script is run twice a day. We know it's working because we see the edits in both the 'Inspector' version and the default version. Everything looks fine in the Esri view of the data table in SSMS as well...just not the base table. To reiterate: looking at the base table, it appears that no records have ever been updated here. The best compress end state count we can achieve is 61 which isn't too surprising given that Esri's offline data mechanism is apparently prone to creating orphan versions/replicas (according to the Geodata analyst i've worked with in the past). I just cannot understand how this base table reflects no changes/edits...looks like a snapshot of the data from ~3 years ago.... ... View more

I should perhaps clarify: according to my query, the most recent edits in the base table show as circa 2019. Which would then mean none of the edits have been compressed? ... View more