topic Database Views vs Joins in ArcGIS Hub Questions https://community.esri.com/t5/arcgis-hub-questions/database-views-vs-joins/m-p/598950#M3023 <HTML><HEAD></HEAD><BODY><P>I wanted to share an issue with the community that we just worked thru.</P><P></P><P>After our open data site went live, one of our customers point out that all our field names in our parcels layer were wrong. &nbsp;Instead of names like gpin, taxmapnumb, source, etc, &nbsp;the name were gisdbvecto, gisdbvec_1, gisdbvec_2, and so on. &nbsp;The funny thing was that the data tab in both ArcGIS Online and open data should the names correctly. &nbsp;After working with ESRI support and doing some research, I found the problem was the join. &nbsp;We had joined our ownership table to the parcels layer. &nbsp;This caused the names to be gisdb.vector.gpin which was then truncated to gisdbvecto since of the character limit with shapefiles.</P><P></P><P>The solution to the problem was to create a database view instead of doing a join the mxd. &nbsp;In a view, you can rename fields to anything you want which prevents extend name. &nbsp;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). &nbsp;You might need to create a view instead.</P><P></P><P>Hope it helps.</P></BODY></HTML> Tue, 25 Apr 2017 13:38:56 GMT KevinDunlop 2017-04-25T13:38:56Z Database Views vs Joins https://community.esri.com/t5/arcgis-hub-questions/database-views-vs-joins/m-p/598950#M3023 <HTML><HEAD></HEAD><BODY><P>I wanted to share an issue with the community that we just worked thru.</P><P></P><P>After our open data site went live, one of our customers point out that all our field names in our parcels layer were wrong. &nbsp;Instead of names like gpin, taxmapnumb, source, etc, &nbsp;the name were gisdbvecto, gisdbvec_1, gisdbvec_2, and so on. &nbsp;The funny thing was that the data tab in both ArcGIS Online and open data should the names correctly. &nbsp;After working with ESRI support and doing some research, I found the problem was the join. &nbsp;We had joined our ownership table to the parcels layer. &nbsp;This caused the names to be gisdb.vector.gpin which was then truncated to gisdbvecto since of the character limit with shapefiles.</P><P></P><P>The solution to the problem was to create a database view instead of doing a join the mxd. &nbsp;In a view, you can rename fields to anything you want which prevents extend name. &nbsp;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). &nbsp;You might need to create a view instead.</P><P></P><P>Hope it helps.</P></BODY></HTML> Tue, 25 Apr 2017 13:38:56 GMT https://community.esri.com/t5/arcgis-hub-questions/database-views-vs-joins/m-p/598950#M3023 KevinDunlop 2017-04-25T13:38:56Z