Latest Contributions by RhettZufelt

You say the map you currently have open, so I'm assuming you are running this from inside Pro? If so, perhaps it's the geoprocessing options set in Options page: You might try with variations of the above settings.  The setting I have here will overwrite the layer if one with the same name is in the active map.  R_ ... View more

Are you using enterprise geodatabase or File geodatabase? I have ran into issues trying to repair geometry with SDE data.  Even if it says it completed, copy to FGDB and the errors are still there. Don't know if this is related to your issues, but can't hurt to check. R_ ... View more

I have had good success with this: item = accGIS.content.get(itemid) clone_results = target.content.clone_items(items=[item]) R_ ... View more

Yup, see this with every ExB app I've made.  Still use WAB for the majority of my maps for this reason. That, and my users have gotten used to their maps loading in 3-5 seconds.  ExB equivelant is taking 30+ seconds depending on the day/time and I constantly get complaints. R_ ... View more

It appears as if the Left/Right image was changed with ESRI's template. My Left/Right Image Viewer app is in Portal 10.9.1.  If I build it in AGOL, I get the Leading/Trailing as well. I even tried cloning my Left/Right Portal App to AGOL, and it is successful, but still changes the test to Leading/Trailing layers when you view it. R_ ... View more

I have something similar where I have multiple featureclasses related to a single 'inspections' table. I set them up as relationship class in Pro, and published to feature service.  However, to get things (popups, adds, etc.) to work properly, I ended up creating a separate GUID field for each FC in the Inspections Table. So, layer1 and layer2 both have GlobalID field, and the Inspections table has a Layer1_GUID field, and a Layer2_GID field.  I then set up a relationship class with Layer1 GlobalID using the Layer1_GUID field as the Foreign key, Layer2 GlobalID using Layer2_GUID, and so on. So, when I add new inspections, it will populate the Layers respective foreign key field with the GlobalID from the respective layer.  This makes it very easy to 'see' what FC originated the inspection. I actually want this is info a "SourceFC" field in the inspections table so I have a trigger on my data that when new feature is added, if the Layer1_GUID field is populated, update SouceFC = Layer1, If the Layer1_GUID field is populated, update SourceFC=Layer2, and so on. Not sure if this will work for you, but might give you some ideas. R_ ... View more

Have you looked at the photo sizes for the latest points collected?  I ask as I have a project in Field Maps that set to capture Small sized photos, and for some reason, randomly at some point, it started collecting them in the device default size (large as they get). This made the images so large they sometimes timed out trying to submit and took forever to download them after that. Looked in Field Maps Designer, and was still set to Small.  Set it to Large and save, then back to Small and save and it 'fixed' the issue and started saving the small sized photos again.  At least, until the next time it changed itself. So, now I routinely check some of the newly collected photo sizes in the Hosted Feature Class, and if/when they start getting huge again, I repeat the FM Designer sequence to 'fix' it. R_ ... View more

I don't have time to wait around for 'Pro' to do it's thing, and since you said you had Desktop, I just did I there.  I just right click in my GDB in ArcCatlog (10.8.2) and select  New -> Mosaic Dataset, then Add Rasters to it, then load into ArcMap to do the rest. It does say it needs a Standard license. R_ ... View more

If you are fortunate enough to have File History enabled on the computer the file is saved on you can right click on the folder in windows, get Properties, and see if there is a Previous Versions Tab: If so, you can go back to any of the date/times listed and get a snapshot of the project at that time/date. R_ ... View more

Could be somewhere else in the code?  Without the iterations and just using arcpy to join the tables and make a feature layer from it, it appears to be working as expected as well as maintaining the joined field FQ names. Python 3.9.16 [MSC v.1931 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license()" for more information. >>> import arcpy >>> infc = r'Database Connections\PublicWorks.sde\PublicWorks.DBO.Streets\PublicWorks.DBO.Ramps_working' >>> intbl = r'Database Connections\PublicWorks.sde\PublicWorks.DBO.ADA_Table' >>> veg_joined_table = arcpy.management.AddJoin(infc, 'RecField', intbl,'Recnum') >>> fields = arcpy.ListFields(veg_joined_table) >>> for f in fields: print (f.name) PublicWorks.DBO.Ramps_working.OBJECTID PublicWorks.DBO.Ramps_working.Corner PublicWorks.DBO.Ramps_working.recnum PublicWorks.DBO.Ramps_working.RecField PublicWorks.DBO.Ramps_working.Note PublicWorks.DBO.Ramps_working.checked PublicWorks.DBO.Ramps_working.AsBuilt1 PublicWorks.DBO.Ramps_working.Photo PublicWorks.DBO.Ramps_working.SHAPE PublicWorks.DBO.ADA_Table.OBJECTID PublicWorks.DBO.ADA_Table.Recnum PublicWorks.DBO.ADA_Table.InvDate PublicWorks.DBO.ADA_Table.Functional_Class PublicWorks.DBO.ADA_Table.Cencus_Tract PublicWorks.DBO.ADA_Table.Block PublicWorks.DBO.ADA_Table.School_Walk_Route PublicWorks.DBO.ADA_Table.Government_Facilities PublicWorks.DBO.ADA_Table.MEF PublicWorks.DBO.ADA_Table.Severity >>> arcpy.management.MakeFeatureLayer(veg_joined_table, 'testjoin') <Result 'testjoin'> >>> fields2 = arcpy.ListFields('testjoin') >>> for f in fields2: print (f.name) PublicWorks.DBO.Ramps_working.OBJECTID PublicWorks.DBO.Ramps_working.Corner PublicWorks.DBO.Ramps_working.recnum PublicWorks.DBO.Ramps_working.RecField PublicWorks.DBO.Ramps_working.Note PublicWorks.DBO.Ramps_working.checked PublicWorks.DBO.Ramps_working.AsBuilt1 PublicWorks.DBO.Ramps_working.Photo PublicWorks.DBO.Ramps_working.SHAPE PublicWorks.DBO.ADA_Table.OBJECTID PublicWorks.DBO.ADA_Table.Recnum PublicWorks.DBO.ADA_Table.InvDate PublicWorks.DBO.ADA_Table.Functional_Class PublicWorks.DBO.ADA_Table.Cencus_Tract PublicWorks.DBO.ADA_Table.Block PublicWorks.DBO.ADA_Table.School_Walk_Route PublicWorks.DBO.ADA_Table.Government_Facilities PublicWorks.DBO.ADA_Table.MEF PublicWorks.DBO.ADA_Table.Severity >>> R_ ... View more

one way would be to create a new Mosaic dataset, then add the SID rasters to it without building overviews.   This will make a Footprint layer (polygons) with the outlines of each input SID image.  You can then 'Export' the Footprint layer to a separate Polygon feature class, and each polygon will have the name of the SID it encompasses in the [name] field. If you delete the Raster field from the 'new' Footprint layer (need to delete the Raster field from this new FC or it won't let you perform a spatial join against it), you could then use this as your polygon layer, or can perform a spatial join against it to populate your polygon featureclass. Not sure if this works for you, but may get you along a path that does. R_  Edit:  This will NOT copy the file extension of the image files, just the name itself. ... View more

Perhaps this post will help?  Looks to be the same issue. R_ ... View more