Problems with "Add Field"

2902
12
Jump to solution
02-17-2016 01:53 PM
BrunaCavalcante
New Contributor

Hello everyone!

I'm having problems to add a field on my shape's attribute table. When i try to add a Double column, it should show the options "scale" and "precision" for me to fill, but it keeps showing the options "alias", "allow null values" and "default value". How can i change that?

Thank you for the help!

P.S.: I'm using ArcGIS 10.

0 Kudos
1 Solution

Accepted Solutions
DanPatterson_Retired
MVP Esteemed Contributor

shapefiles don't support alias

Add Field—Help | ArcGIS for Desktop

other readings

Working with fields in shapefiles by adding a field in ArcCatalog—Help | ArcGIS for Desktop

in geodatabase you can only change properties when the table is empty,

Alter Field—Help | ArcGIS for Desktop

and shapefiles would be the same

View solution in original post

12 Replies
AdrianWelsh
MVP Notable Contributor

Make sure you're not in an edit session. I presume you changed the dropdown box to Double (or float or whatever the option is).

If it still persists, close all ArcMap sessions and try it again after reopening your map.

0 Kudos
BrunaCavalcante
New Contributor

Hello Adrian.

I already tried that and it didn't work...

0 Kudos
AdrianWelsh
MVP Notable Contributor

Can you paste a screen shot of what you're seeing exactly?

0 Kudos
BrunaCavalcante
New Contributor

d646bfe0-6a69-4737-88e5-26665c4b9aad.png

Here... This happens with all column types...

0 Kudos
KyleBalke__GISP
Occasional Contributor III

Interesting...I have the same issues (running 10.2 and 10.3).

0 Kudos
BrunaCavalcante
New Contributor

Yeah, it's the exact same thing! But i need it to show "precision" and "scale"

0 Kudos
DanPatterson_Retired
MVP Esteemed Contributor

see my link below... precision and scale will vanish once the field is created but it is still visible in the properties of the table

0 Kudos
AdrianWelsh
MVP Notable Contributor

Ok, this is weird. I am seeing the same things too (running ArcMap 10.3.1 on a Basic license).

However, these was happening with a File Geodatabase.

When I tried with a plain ole shapefile, it worked like it was supposed to...

Maybe setting precision and scale are not necessary within geodatabases? (but that doesn't sound right...)

0 Kudos
DanPatterson_Retired
MVP Esteemed Contributor

I thought that was one of the magical things about geodatabases... there is no need to set them since they are controlled by the gdb themselves.. and from my link

  • When you create a float, double, or integer field and specify 0 for precision and scale, the tool will attempt to create a binary type field if the underlying database supports it. Personal and file geodatabases support only binary type fields, and precision and scale are ignored.