Allow Field Precision and Scale to be Defined in Feature Class Wizard

[mpboyle]

When adding a "double" field type in ArcGIS Pros Feature Class Wizard, please allow precision and scale to be defined if using an enterprise geodatabase.

For example: if I add a double field to an enterprise geodatabase dataset within the wizard, the precision and scale can not be defined, and this results in them being 38,8.  In most of our use cases this far exceeds any precision and scale we'd use and bloats the table.  If I want to alter the precision and scale, I have to manually do it through the database interface like SSMS.

[RonnieRichards]

@SSWoodward 

@mpboyle is correct I don't think the option to specify precision in the Create Feature Class/Table wizards have ever been present in a Pro release. 

The right click within an Enterprise Geodatabase in Catalog is one of the quickest navigations for new tables in Catalog. Right click create a new table and import from a template. 

As an educator students are going to gravitate to the context tools before searching for geoprocessing tools so please make them behave consistently. Your future ArcGIS Desktop users will appreciate consistency and really enjoy creating GIS data models in the Enterprise GDB especially considering this requires Professional Plus licensing to "create" in an EGDB.

This was a solid workflow in ArcMap

[Michele_Hosking]

And you know what - it's not all about the Create Feature Class/Table wizards in Pro.  It's the fact that somewhere along the line (and this did happen during the ArcPro days) the default for a double field in an enterprise geodatabase has changed from 38/8 to 7/1. Now 38/8 is a little ridiculous I grant you but at least it's useful. It allows you to put whatever you like in the field so if someone forgets to change the precision it's still going to work.  7/1 is just a pain in the proverbial. As part of this can we please have this default changed to something sensible otherwise we will still be having the issue of finding out that a field doesn't have enough decimal places after a feature class /table has been created due to over-looking the 7/1 precision default and be back in the stupid position of having to recreate a table just to fix this issue.

[RonnieRichards]

@Michele_Hosking you are absolutely correct with that!!

This appeared to happen in the 3.2 release when the other GDB changes were introduced. Pro 3.2+ double data types are created as 7/1. This release also seems to break the FLOAT datatype.

Tables created prior to 3.2 release double data types were defined as 38/8.

[PhilippeChesselVdG]

Hello,

Yes , i am totally in line also with @Michele_Hosking , the problem is the change in 3.2 for Double and Float that has no logic and no justification for it. (Or ESRI should give us any good reason or that , i can hardly find any ?) 

And it is complicating a lot the life of end users.

The best option would be to allow scale and precision definition into the Add Table/Class wizard.