Since we updated to ArcGIS Pro 3.2 we have issues with our Enterprise databases. One of the issues is, that we cannot write to them...
New data types such as 'date only', object ids are now 64 bit instead of 32 bit, etc.
With a test database I luckily had laying around I attempted an upgrade from 11.0.0.3.9 to 11.2.0.49743. Not that I could have selected any lower database version!
The upgrade went well and now I am able to write data again to this database! However, the next that is throwing stones in my way is sharing the data as a web layer to our Enterprise portal.
When analysing the layer I am getting the following error:
We actually never had the intention to upgrade our portal (10.9.1) to 11.2, since 11.2 is a short-term support release, while 11.1 is a long-term support release.
Could it be that we are forced to upgrade to a short-term support release, simply because ArcGIS Pro 3.2 does not support the long-term support release? It kind of makes the whole thing ridiculous.
- We are living in the 21st century.
GIS moved on and nobody needs a format consisting out of at least three files! No, nobody needs shapefiles, not even for the sake of an exchange format. Folks, use GeoPackage to exchange data with other GIS!