Latest Contributions by MJBiazar

Hi @bgomes, I've ran into a similar issue and I believe it happens only when you reference the image question name in the constraint. Please change your constraint from "count-selected(${photo})<4" to "count-selected(.)<4" and see if it resolves the issue. Best, MJ ... View more

Hi @MeghJones , Although Workforce allows certain configuration for the integration URL through the web app, you can modify the integrated URLs for any of the apps that your Workforce project is integrated with by editing the "Assignment Integrations"  table in the hosted feature layer for your project. In this case, to add a callback parameter to the URL to return to Workforce app after submitting the form in Survey123 app, you can append "&callback=https://workforce.arcgis.app" to the URL.   Best, MJ ... View more

Hi @HayleighFisher, You can add attachments through different methods including a WAB application, however, only attachments that are submitted through Survey123 app will have attachment keywords that is what Survey123 uses to associate an attachment with a question in your survey.  The attachments with no keyword (like the ones submitted via a WAB application), won't show up on the survey form when you are trying to edit an existing survey record in Survey123 app (via Inbox or in edit mode in web app). You can update existing attachments from the REST to add keywords to the attachments that are not submitted through Survey123 app.  Open the Data tab in Survey123 website. Click on the record with the image attachment missing the keyword Right-click on the attached image and open in new tab Note the attachment id in the URL (in this example, it’s 31): https://services.arcgis.com/Wl7Y2PbjtJs5n/arcgis/rest/services/service_84a27/FeatureServer/0/14/attachments/31?token=2fr... Replace the “attachments/<attachment_id>” with “updateattachment” in the URL. Your URL should look like this https://services.arcgis.com/Wl7Y2PbjtJs5n/arcgis/rest/services/service_84a27/FeatureServer/0/14/updateattachment?token=2fr... Fill out the form: The Attachment ID is listed in the URL after /attachments (from Step 4). The Keyword is the name of the image question that you want to associate this image with. Click Update Attachment. Notice that this image now shows up under the image question in form view and will be printed in the report.     Best, MJ ... View more

Hi @HayleighFisher, That is correct! The capability to edit attachments for existing submissions via Inbox was introduced in 3.13. If you do not see the existing data for any of the questions within your repeat, your survey is probably missing query parameter. To load data from the related table (including attachments) in the Inbox, you have to make sure that your survey has been configured properly to allow querying data from the related layers.  You need to add "query allowupdates=true" in "bind::esri:parameters" column in your XLS form for your begin repeats, republish your survey, and update the survey in field app on your device. This will query the existing attributes from the related table along with the attachments and allows editing. You can find more details about this here:  https://doc.arcgis.com/en/survey123/desktop/create-surveys/prepareforediting.htm#ESRI_SECTION1_80CFFC9C38654DC293D4F36C5376C62E   Also, image attachments may affect how images show up in reports where images that are missing attachment keywords may not show up when ${<image_question_name>} syntax is used in the template. In ArcGIS Online and ArcGIS Enterprise version 10.8.1 and later where attachment keywords are supported, attachments will have attachment keyword as long as the images are added via Survey123 app (field app or web app). However, if attachments are added to a feature through a method other than a survey, for example in ArcGIS Online Map Viewer, ArcGIS Pro, other field apps such as Field Maps, they won't have the attachment keyword.   Best, MJ ... View more

Hi @RobBlash, it is not possible to have ObjectId as a question when publishing a survey. Whether if you publish a new survey or use a submission URL to an existing feature service, you won't be able to publish and you'll get an error. This is expected since the ObjectId field is essentially a non-editable field and besides ObjectId only gets created after you submit a form.    However, you may need to use the ObjectId of your existing submissions on your form for different reasons. For instance to append the ObjectId to a URL to create a link to send a query request or generate a link to Survey123 website and select a submission using the ObjectId parameter.      There is a workaround that enables you to pull ObjectId of existing features and pass it to a field on the form and use it in calculations as needed when editing existing survey submissions. In order to do this, you can add a question (with any type such as text, integer)  to show ObjectIdss. The name for this field should match the name of the ObjectId field of the feature layer (case sensitive). You also need to set the bind::esri:fieldType to "null". By doing this, you will be able to publish your survey without any errors.     Best,  MJ ... View more

Hi @JoshuaBruni I have not seen this error before when saving a map but it would be helpful to take a closer look at your data. I have a few question to understand the environment of this issue better: Can you create a map with the same layer in Classic Map Viewer? If your layer/map is shared publicly, do you mind sharing the URL/item ids? Is your layer time enabled? If so, can you try disabling it (at least temporarily) and see if you can save your web map? Thanks!  MJ ... View more

Hi all,  It seems like this issue is caused by a defect in Map Viewer. A bug has been logged against this behavior: BUG-000139878 - Hidden fields are visible and editable when editing a feature service in Map Viewer.   Best, MJ ... View more

Hi all,  It seems like this post has not been active for a while but I wanted to share another cause for similar issues like this for reference here.  Export data as filegeodatabase fails if you have a domain with codes that don't match the field type. For instance, if you have an integer field that has sting codes in domain list. On of the ways that this could happen is publishing a survey from Connect with a select_one question with integer/double type while the choices on the choice list contain string.  In that case, not only the export fails, but also the strings that are being passed to a non-string field will be dropped during submission which is expected due to the error design that causes mismatch between the field type and domain.   Best, MJ  ... View more

Hi all, It seems like the "Error Code: 400 not licensed by user" when trying to delete a member was due to a defect in ArcGIS API for Python (1.8.X).  This has been addressed in 10.9 version.  ... View more

Hi @HaroldHerrera1 , I was able to confirm that using select_one_from_file instead of select_one_external does not reproduce the error and works as expected in both field app and web app. Attached is a sample survey that you can use to test this workaround. ... View more

Here is the details for the defect: BUG-000144749 - Survey with external select published from Survey123 Connect cannot be accessed in web app returning an error "This survey cannot be accessed in the web app. Please contact the survey owner to republish the survey with 'Create web form' enabled. Error: Missing .webform file." ... View more

@HaroldHerrera1 @FionaBarry  Thanks for the confirmation! Having external_choice questions seams to be the cause of the error. A defect has been logged against this behavior by Esri Technical Support and will be reviewed soon to determine the best actions to address this issue. ... View more

Hi, There has been reports of similar issues and we are trying to narrow down the issue to identify the root cause. Can you please confirm if you are using external choices in your survey? Thanks, MJ   @WetherbeeDorshow @HaroldHerrera1 @FionaBarry  ... View more

Hey @JessicaGough , Thanks for confirmation. This is great news! 🙂 ... View more