Latest Contributions by KevinDunlop

I wanted to share an issue with the community that we just worked thru. After our open data site went live, one of our customers point out that all our field names in our parcels layer were wrong.  Instead of names like gpin, taxmapnumb, source, etc,  the name were gisdbvecto, gisdbvec_1, gisdbvec_2, and so on.  The funny thing was that the data tab in both ArcGIS Online and open data should the names correctly.  After working with ESRI support and doing some research, I found the problem was the join.  We had joined our ownership table to the parcels layer.  This caused the names to be gisdb.vector.gpin which was then truncated to gisdbvecto since of the character limit with shapefiles. The solution to the problem was to create a database view instead of doing a join the mxd.  In a view, you can rename fields to anything you want which prevents extend name.  So if you are serving up your data with joins, you might want to check it (ie download it via open data and open it in ArcMap).  You might need to create a view instead. Hope it helps. ... View more

My co-workers and I can't seem to log into Open Data using the Microsoft Edge browser.  Viewing pages that don't require a log in work but the login freezes and then gives an error 500.  I have tested this using my work and personal computers. Anyone else experiences this? ... View more

In ArcGIS Pro, is there anyway to see what privileges are assigned to a SDE feature class or table?  Help documentations says to use the Change Privileges geoprocessing tool to change existing privileges but that tool doesn't allow you to see what already assigned.  In ArcCatalog, this option used to be under the manage option in tooltip popup.  Having the ability to see what is assigned already in an important feature when managing databases. ... View more

Currently, when you disable archiving in SDE, you can choose to save the history table as a new feature class.  However, there is no way to re-attached that saved history table when you re-enable archiving.  This is a problem when you need to briefly turn off archiving to make changes to the layer or to copy it from one database to the other.  If there was a tool to re-attach the archive table to the feature class, it would allow for a more complete archive history.  This could cause a "false gap" in the history if edits were made during the time archiving was turned off, but the DBA should still be given the option. An additional option to this solution would be to allow the user to attach multiple archiving table.  This way the DBA could save off each year as a new archive table but still be able to attach them as needed.  In this case, the tables would be attached to the historical version tree but the records would not be imported into active archive table. ... View more