Get rid of add-on user type extensions

Idea created by nfazer_midlandcounty on Oct 9, 2020
    New
    Score90
    • nfazer_midlandcounty
    • E07016@srcity.org_SantaRosa
    • Katrin.Meschin@harku.ee_harku
    • konzelt
    • philna_BMI
    • thant_zin_oo
    • jerome.haaland
    • cstewart@fortsask.ca
    • JPlatt@mesaaz.gov_MesaAZ

    I see this is a new way for Esri to confuse use with complicated licensing. We're trying to test out editing the parcel fabric with Portal in Pro and I now see that fabric editing requires a user add-on extension license. If we want 1 person or 10 people to be able to edit OUR parcel data, we shouldn't have to pay for an extension and then assign it to a named user. In the Desktop/database parcel fabric, we could have as many versions as we needed. Now this is restricted because it's a service? We should be able to create as many versions and have as many people edit parcel fabric as we want without having to add licenses and more money into the mix.

     

    Give us flexibility to control parcel fabric editing through roles or permissions or something we already have available to us. Don't force us to use complicated licensing for something that doesn't need licensing.