Pro: When creating a feature class, Z value should default to "No" (Like Arc)

Idea created by tpcolson Champion on May 29, 2018
    Reviewed
    Score20
    • tpcolson
    • shlousek

    In Pro 2.1.2, when creating a new feature class, "Z Value" defaults to "Yes", forcing the majority of Pro users whom do not map in 3D to have to remember to set it to "No". This is especially problematic when that feature class is going to be used in a downstream feature service in ArcGIS Server, which whines and complains about null Z values. Yes, I can remember to set it to no, and yes, I can configure the feature service default Z value, but, these are all extra steps that aren't required in the Arc Map new FC workflow, and I'm going to have a heck of time getting folks to remember to set that to "No".