Latest Contributions by RhettZufelt

suspect you are using a File Geodatabase for this?  FGDB's do not support unique GlobalID's. You will need to copy the data to an enterprise or mobile geodatabase in order to have a unique index on the GlobalID field and it will then honor the "Preserve GlobalID's setting" in the append tool. R_ ... View more

You can also select the labeling tab in the TOC and copy the label class(es), then it lets you choose which options to paste to other classes: R_   ... View more

Suspect the issue is not being able to have two FC's in the same database with the same name regardless of them being in a Feature Dataset or not. So, would probably have to do as ESRI suggests, go to different database, delete, copy back.  Or, script it so that it changes the name, copies, deletes and renames. R_ ... View more

Do you have access to Map or Pro?  There are tools in both to sort/export domain tables, just can't use it to update the hosted data. I do this with arcpy and the python API if you have access to them.  Just need to get them into a sorted table with Code and Description.  Then I use the following code to get it into the correct format: def CreateDict(fieldname,domainname): global update_dict update_dict = {"fields": [ { "name": fieldname, "domain" :{"type" : "codedValue", "name" : domainname, "codedValues" :[ {"name" : "Pathway", "code" : "Pathway"} ]}}]} infc = BASE + os.sep + 'domaintable' # sorted table with domain Code and Desc. with arcpy.da.SearchCursor(infc, ["Code","Street"]) as cursor: for row in cursor: update_dict['fields'][0]['domain']['codedValues'] += [{"name" : row[0] , "code" : row[1]}] In this case, I am adding "Pathway" as I need it in my list, but is not in the table and will be at the top of the domain list. this will format the update_dict to the proper format, then I use the API to get the layer and update it. Example Output for the proper format: update_dict = {"fields": [ { "name": "Street", "domain" :{"type" : "codedValue", "name" : "Streetnames", "codedValues" :[ {"name" : "Pathway", "code" : "Pathway"}, {"name" : "89 PR SE", "code" : "89 PR SE"}, {"name" : "952 PR SE", "code" : "952 PR SE"}, {"name" : "974 PR SE", "code" : "974 PR SE"}, {"name" : "9th St", "code" : "9th St"}, {"name" : "Aaron Dr", "code" : "Aaron Dr"}, {"name" : "Abbot St", "code" : "Abbot St"}, {"name" : "Abert Ave", "code" : "Abert Ave"}, {"name" : "Acacia Ave", "code" : "Acacia Ave"}, {"name" : "Ada St", "code" : "Ada St"}, {"name" : "Adair Ct", "code" : "Adair Ct"}, {"name" : "Adair Dr", "code" : "Adair Dr"}, {"name" : "Adams St", "code" : "Adams St"}, {"name" : "Addison St", "code" : "Addison St"}, {"name" : "NA", "code" : "NA"} ]}}]}   lyr = my_agol.content.get('xxxxxxItemIDxxxxxxxxx').layers[0] # get the layer to update update = lyr.manager.update_definition(update_dict)    R_ PS, unless there is a need to have the code different that the description, would highly suggest you keep them the same (as in my example above, or @Katie_Clark's example) as you will have better results with fewer issues in the future.   Domains don't all work the same in each client.  sometimes it searches code, sometimes domain, sometimes displays one and not the other.  The only way for it to be 'bulletproof' is if they are both the same. ... View more

Have you looked at the troubleshooting logs in Field Maps App?  That might give a better idea of what is going on. I say that as the two errors in the log you posted seem to appear at least once or twice a day since AGS 10.6.1 (still in 10.8.1 and 10.9.1) and tech support finally gave up on trying to figure out why.  So, I kind of doubt it is related to the offline issue. Never seems to cause any issues that we've noticed.  But, I have not tried offline with Portal, nor branch verioning. R_   ... View more

Have you tried it without the matching field option? Since you say you are deleting the appended rows, I assume they are not initially in the target dataset. I'm wondering if you SQL  expression is working, but, the matching field option is then 'updating' the filtered out rows since they are 'missing' in the target. If this is the case, testing without the matching field option would not append the blank/null value rows. R_ ... View more

just ran into this issue the other day myself, but with ArcMap. In my case, somehow (suspect because I tried to use Pro's versioning manager at some point)  the traditional versioning move edits to base was no longer applied to all the tables in the FeatureDataset (or in this case, at the root level).  Always seem to have issues whether or not Pro will actually change the traditional versioning or not, or mess it up. So, opened good old reliable ArcCatalog, selected Table B and un/re-registered with move edits to base. Next edit attempt on Table A give save error, but for Table C.  Used Catalog to re-register Table C with move edits to base and all is happy now. Most of my data that has versioning move edits to base are in Feature Datasets, so this usually isn't an issue. But, it appeared as if all the tables in root behave as if in a Feature Dataset except each table has to be versioned separately. Not sure if this applies to your case, but checking that all the FC's/tables in the level of Table A to make sure the versioning is the same might help resolve it. R_ ... View more

Sure, just click on the List by Selection tab and you can toggle between selectable and not. R_ ... View more

Looks like I should have read the original post more closely (about the link), not just skipping sign in. But, working with tech support, we found no way to skip sign in and see or search for any maps available on your portal, just AGOL. R_ ... View more

However, this only applies to AGOL, and not to Portal. R_ ... View more

You say there was a change in the database that broke it. What was the change? R_ ... View more

If I understand correctly, in Pro, you can activate the table, hold CNTRL and roll the mouse wheel, it will change the font size of the table to get the font size you need. R_ ... View more

Sure you can. Just go to the Item Details page, Data tab and you can do it there. R_ ... View more

Sure, but I don't think I have that bug issue as I still only have one relationship class on each featureclass. Also, to clarify, I am running this on Enterprise 10.9.1 with registered feature services on SQL server database. The relationship classes were setup on the data, then published to Enterprise portal with ArcGIS Pro. Showing relationship class between Manholes FC and StormTrackingTable (Inspections table).   Showing relationship class between Inlets FC and StormTrackingTable (Inspections table).   Plus I have relationship classes set up on all the other FC's to be inspected, but these two should give the idea. Here are the relevant fields in the Inspections table: and a snippet of part of that table: So, a Manhole inspection puts the relative Manhole GlobalID into the ManholeGUID field, Inlets into the InletGUID field, etc.  I also populate the RelGlolabID field with the same feature GlobalID, along with the SourceFC field of the FC being inspected.  This makes it much easier in processing to be able to just query by SourceFC and GUID when needed. Then, in FMA, select Manhole with existing Inspection, select one of the inspections and :     R_       ... View more