Allow NULL value setting at Map level vs Database level for Collector

Idea created by mwawryk on Jan 9, 2020
    New
    Score50
    • mwawryk
    • dvanriel
    • diannea
    • JustinT
    • A_King

    Currently you can set allow NULL values at the feature class and feature table level but it only works for non-versioned data. We would like to have the option to set it in a map document so that is is easily enforced at the service level in applications such as collector. The field details show what the database has but if a second option was added like it was for Read-Only at the map level it would allow much greater flexibility without having to edit the service post publishing if that is even possible. So far it seems you can only change the value on hosted services but we edit on the geodatabase mostly.