nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Republished choice updates do not appear in feature layer

vanessagiles

I edited the choices to an existing survey and republished it successfully however these changes are not reflected in the feature layer in arcgis online. What else do I need to do to see this change? (urgent!!) The changes are available in the app but not online.

Trouver plus de publications taguées avec

Accepted answers

All comments

JamesTedrick

Hi Vanessa,

Survey123 Connect does not currently update the domain when republishing surveys. This is partially because if values have been entered that have been subsequently removed, those would not be displayed. As a workaround, you can manually update the domain with the values; see Updating Hosted Feature Services in ArcGIS Online | ArcGIS Blog

vanessagiles

Thanks very, James, this seems like the right answer however I am unable to save the changes. I have only changed the choices options for one list but cannot update the service:

vanessagiles

Invalid Definition

Thanks very, James, this seems like the right answer however I am unable to save the changes. I have only changed the choices options for one list but cannot update the service - please see error message.

JamesTedrick

Can you provide a copy of the UpdateLayerDefinition text? JSON is highly structured format that is easy to get a bit wrong. you can also try validating at http://jsonlint.com - it's good for checking that the text is valid.

vanessagiles

This is the section that I have updated but the errors seem to be from existing code. I changed the code for "Unsure" and added "Mauve". The code saves ok but then if I try adding new point data Mauve is still not showing as an option.

    {
      "name" : "bandLT",
      "type" : "esriFieldTypeString",
      "alias" : "Band colour - LEFT TOP",
      "sqlType" : "sqlTypeOther",
      "length" : 4,
      "nullable" : true,
      "editable" : true,
      "visible" : true,
      "domain" :
      {
        "type" : "codedValue",
        "name" : "cvd_bandLT",
        "codedValues" : [
          {
            "name" : "Make Selection",
            "code" : "ms"
          },
          {
            "name" : "Unsure",
            "code" : "Un"
          },
          {
            "name" : "Black N",
            "code" : "N"
          },
          {
            "name" : "Orange O",
            "code" : "O"
          },
          {
            "name" : "Green P",
            "code" : "P"
          },
          {
            "name" : "Mauve U",
            "code" : "U"
          },
          {
            "name" : "Yellow Y",
            "code" : "Y"
          },
          {
            "name" : "White W",
            "code" : "W"
          },
          {
            "name" : "Blue B",
            "code" : "B"
          },
          {
            "name" : "Red R",
            "code" : "R"
          },
          {
            "name" : "Pink K",
            "code" : "K"
          },
          {
            "name" : "Metal M",
            "code" : "M"
          },
          {
            "name" : "Wild (unbanded)",
            "code" : "Wild"
          }
        ]
      },
      "defaultValue" : null
    },

Anonymous User

James,

Will this be an enhancement within version 2.0? After some reading that I have done I was under the impression that the domains were updated if you did not change the form schema?

Which is confusing after having the dialog within Survey123 Connect referencing that your data will remain even though we are republishing? IT WOULD be awesome if the survey could be updated to include "New or Additional" Domain values, but not allow for the removal of previously posted domains.

JamesTedrick

Hi Mike,

The behavior has not been revised as of version 2.0. In our documentation, we refer to choice lists, which can be stored as domains (but are not required to); the revision of choice lists does not result in a schema change. I've added this request to our development backlog for evaluation & prioritization.

Anonymous User

James,

Thank you for the response. Two more question, but does this same logic apply to using pulldata or external picks; in terms of the FGDB Domains not being updated with the picklists?

Last question, when I do go back and update the choices or the comma-delimited text file from the media folder for the external picks; will the answer of the newly added choices show up within the FGDB feature class or related table? If so, then that is an acceptable behavior for me.

I do greatly appreciate the information.

Mike

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.