|
POST
|
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
yesterday
|
0
|
0
|
32
|
|
POST
|
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
Monday
|
0
|
1
|
87
|
|
POST
|
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
Thursday
|
1
|
2
|
233
|
|
POST
|
I use the Export to CAD tool for this. Does not help with determining orientation, but in number 2 above, it sounds like you have a way to get orientation of the points, just not showing in CAD. The 'trick' is adding all the required CAD fields to the featureclass before performing the export and using a CAD seed file that has all the blocks the drafters use in it already. I took existing CAD file the drafters use, deleted all the entities and save as new file. this file has all the blocks in it for the seed. I'm sure you could use the Add CAD Fields tool, but I just use arcpy.AddField as I only need some of them for my point export. I use a csv file to configure my import including the input featureclass I am converting, the Layer name (layer name in CAD file), the query selecting the items I need from the featureclass (if only exporting subset), the LyrColor, Color, Block (block name in CAD seed file), CadAngle, LyrFrzn and Scale (normally = 1 in my case). However, these values can be hard coded as well. Then I create each of the fields in the new featureclass and calculate the values from the csv file/featureclass field(s) into the new CAD fields. Then I export the new featureclass to CAD: arcpy.conversion.ExportCAD(InFC, "DWG_R2018", Output_dwg + ".dwg", "Ignore_Filenames_in_Tables", "Append_To_Existing_Files", seed_file) Then, in the output CAD file, all the features are there, assigned to the appropriate Block and Layer, color, scale, rotated, etc. Keep in mind that unless changed in CAD, it uses due East as Zero degrees and positive is counterclockwise from there. (In my CadAngle in the csv above, you can see for one featureclass I add 90 to the value currently stored in the !Rotation! field so that it aligns correctly.) Sounds a bit complicated, and takes a bit to set up, but I have been exporting my GIS data to the CAD design group using this for years. Hope this helps, R_
... View more
a week ago
|
0
|
0
|
136
|
|
POST
|
Sure, just click on the List by Selection tab and you can toggle between selectable and not. R_
... View more
a week ago
|
0
|
0
|
101
|
|
POST
|
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
2 weeks ago
|
0
|
0
|
290
|
|
POST
|
You say there was a change in the database that broke it. What was the change? R_
... View more
3 weeks ago
|
0
|
0
|
556
|
|
POST
|
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
04-09-2026
07:34 AM
|
0
|
0
|
141
|
|
POST
|
Sure you can. Just go to the Item Details page, Data tab and you can do it there. R_
... View more
04-08-2026
11:01 AM
|
0
|
1
|
302
|
|
POST
|
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
04-02-2026
09:50 AM
|
1
|
1
|
467
|
|
POST
|
Do each of your storm assets have their own related table, or are you using one table for all of them? Not sure if it's related, but I had several issues going from my Sewer inspection app to my Storm inspection app because of the multiple asset types and using a single table for all of my storm inspections, even though the GUID is unique. Easiest fix was to have a separate storm inspection table for each of the storm assets. However, for local reasons, we wanted all the storm inspections in one table, regardless of asset type. Once I created a separate GUID field for each of the assets in the storm tracking table, then set up a relationship class on each asset pointing to its specific GUID field in the inspections table, all the weird relationship confusion went away. Just tested it and I do see and am able to copy previous inspections. Hope this helps, R_
... View more
04-01-2026
01:21 PM
|
1
|
4
|
514
|
|
POST
|
saw that, but response had no indication that it was tried.
... View more
03-30-2026
12:44 PM
|
0
|
0
|
433
|
|
POST
|
do you still get the error when you click the folder button and browse to the input surface, and NOT select it from the dropdown? R_
... View more
03-25-2026
04:05 PM
|
0
|
2
|
578
|
|
POST
|
Yes, that gets very annoying when you are panned to the area you want to make a point and it pans you back to your GPS position. That setting is controlled in Field Maps designer App Settings: R_
... View more
03-24-2026
03:48 PM
|
0
|
0
|
396
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Thursday | |
| 1 | 04-02-2026 09:50 AM | |
| 1 | 04-01-2026 01:21 PM | |
| 1 | 10-08-2025 11:59 AM | |
| 1 | 09-05-2025 03:16 PM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|