Latest Contributions by MJBiazar

Hi @JosephKerski The stakeholder view gets automatically created when you share your survey results from Survey123 website. However, this specific view layer is created for a specific purpose which is controlling who can access the results of your survey. However, you can use this view for other purposes.  Besides, as it's mentioned in the documentation you linked in your previous post here, you can always create other views if you need from the item details page of your survey's hosted feature layer. Can you please explain why creating a view layer manually didn't work? Were you getting any errors?   Thanks, MJ ... View more

Hi @jbauer I'm able to reproduce the issue you are experiencing with a survey I published  with your XLS form. It seems like the error is reproduced when a repeat with relevant expression has a dynamic repeat count. For example, there is a repeat in your survey called "activity_prod". This repeat has a relevant expression "selected(${co2_activity_type},'Producer')" and the repeat count is determined by another question ("${num_prod}").    Removing the calculation for the repeat_count and replacing it with a number resolves the issue but it may not be a viable workaround.  On the other hand, removing the relevant expression for the begin repeat and adding it to the questions inside the repeat which also resolves the error might be a better workaround for you.    I recommend reaching out to Technichal Support to report this issue and log a defect against it if needed.    Best, MJ ... View more

@RainbowUnicorn Fantastic! I'm glad that you are not experiencing the issue on your personal computer. I agree with your assessment as well. The issue seems to be specific to your work environment (the machine, network, etc.) ... View more

@RainbowUnicorn I'm sorry to hear that you are experiencing a different issue while trying to publish a copy of your survey (you may find this post helpful). Whatever is causing this issue may be related to the issues you were experiencing with your original survey. I think at this point it's best for you to create a case with Esri Technical Support to take a closer look at your issue and continue troubleshooting.  ... View more

Hi @RainbowUnicorn ,  I have a few questions to have a better understanding of the environment of your issue: Are you working in ArcGIS Online or Enterprise? Are you experiencing this issue after republishing a survey that was working before? If so, what changes did you make?  Do you get the same error if you publish a copy of this survey? (make sure that "Create web form" is enabled when publishing)   If possible, can you share the XLS form for your survey?    Thanks, MJ ... View more

Hi @DEI , When creating a relationship class, you can specify the Forward/Backward Path Label. These labels are carried over to the hosted feature layer. This label is what FeatureSetByRelationshipName( ... ) uses to reference a relationship in a feature service.  If you export your feature layer as a file geodatabase from ArcGIS Online, the Forward/Backward Path Labels are dropped, so when the layer is published back to ArcGIS Online, the relationships in the hosted feature won't have the labels initially specified when the relationship class was created.  A defect (#BUG-000149669) has been logged against this behavior. In the meantime, it seems that in the meantime, the workaround is to recreate the relationship class in Pro and reassign the Forward/Backward Path Labels.   Best, MJ ... View more

@Sven_Harpering Fantastic! I'm glad that it worked for you too.  ... View more

Hi @MikeCooperstein , If you are collecting your inspection data into a related layer, you can use a data expression like the example below to query the related record with the most recent data and use it as a data source for the list widget on your dashboard. Make sure to modify the script according to your environment and your data schema (e.g. item id, field names, etc.) // Create a featureSet from the related table. Replace the ITEMID and LAYERID to reference your related layer. var portal = Portal('https://www.arcgis.com'); var relatedTable = FeatureSetByPortalItem( portal, 'ITEMID', LAYERID, ['*'], false); // Identify unique values in the FOREIGNKEY field to use in filter statement later. Replace FOREIGNKEY with the name of the field that the relationship is based on. var uniqueFkeys = Distinct(relatedTable, ['FOREIGNKEY']); // Define a dictionary to write the attributes of the selected features into. Field names here are optional and you need to specify the field type based on the data that you want to write into each field. A table created from this dictionary is the final output of this script. var dict = {'fields': [ {'name': 'FIELDANAME', 'type': 'esriFieldTypeString'}, {'name': 'FIELDBNAME', 'type': 'esriFieldTypeString'}, {'name': 'FIELDCNAME', 'type': 'esriFieldTypeDate'}], 'geometryType': '', 'features': []}; // Query the records for each feature based on another field. For instance, you can query the most recent inspection of each site, or the inspection with the highest reading for each site. In this example, related records are filtered by DATEFIELD to return the most recent inspection. var index = 0 for (var x in uniqueFkeys) { var id = x.FOREIGNKEY; var filterstatement = ('FOREIGNKEY = @id'); var filtrecords = Top(OrderBy(Filter(relatedTable, filterstatement),'DATEFIELD DSC'),1); // Populate attributes from the selected features into the fields in the dictionary. In this example, FROREIGNKEY, FIELD1, and DATEFIELD are used. You can replace these with the name of the fields from your related table that you want to include in the final table. for (var y in filtrecords){ var FIELDAVALUE = y.FOREIGNKEY; var FIELDBVALUE = y.FIELD1; //Dates should be converted to number to write into a date type field in the dictionary var FIELDCVALUE = number(y.DATEFIELD); // populate the attributes of the selected feature into the dictionary dict.features[index] = { 'attributes': { 'FIELDANAME': FIELDAVALUE, 'FIELDBNAME': FIELDBVALUE, 'FIELDCNAME': FIELDCVALUE }}; } index += 1; } // return the featureset with selected records from the related table return FeatureSet(Text(dict));   All the best, MJ ... View more

Hi @tc_ton, for hosted feature layers in ArcGIS Online, currently, if the layer's editing settings only allows "Add" and  "What features can editors see?",  'Editors can't see any features, even those they add.' option is selected, the Query capability will be disabled for the layer. When the query is disabled, if the layer is opened in Map Viewer Classic, features won't draw and you get "Accessing data failed" error if you try to open the attribute table.    In Map Viewer, features are visible on the map but you don't see the option to open the attribute table.    If you try to use this layer as the data source in some of the apps (e.g. Dashboard), you may get an error and data from this layer may not be accessible by the app.    Since Survey123 3.14, the feature layers that are created for surveys have these editing settings by default. This was an intended change to provide the most secure data experience for survey creators by default and allow them to decide what permissions they want to open on their data. You can enable the query capability by changing the layer settings: Enable 'Update' or 'Delete'. Change the option for 'What features can editors see?' to 'Editors can see all features' or  'Editors can only see their own features (requires editor tracking).' Disable editing.   Best, MJ ... View more

Hi @tc_ton, for hosted feature layers in ArcGIS Online, currently, if the layer's editing settings only allows "Add" and  "What features can editors see?",  'Editors can't see any features, even those they add.' option is selected, the Query capability will be disabled for the layer. When the query is disabled, if the layer is opened in Map Viewer Classic, features won't draw and you get "Accessing data failed" error if you try to open the attribute table.    In Map Viewer, features are visible on the map but you don't see the option to open the attribute table.    If you try to use this layer as the data source in some of the apps (e.g. Dashboard), you may get an error and data from this layer may not be accessible by the app.    Since Survey123 3.14, the feature layers that are created for surveys have these editing settings by default. This was an intended change to provide the most secure data experience for survey creators by default and allow them to decide what permissions they want to open on their data. You can enable the query capability by changing the layer settings: Enable 'Update' or 'Delete'. Change the option for 'What features can editors see?' to 'Editors can see all features' or  'Editors can only see their own features (requires editor tracking).' Disable editing.   Best, MJ ... View more

Hi @Rice_GIS , You can keep the apostrophes in the actual attribute values and use an Arcade expression to encode the values from that field to replace  " ' " with "%27" to include the encoded values in the URL instead of the actual values that contain apostrophes.    Original URLs: https://survey123.arcgis.com/share/dd4b8079b72e480ca429824e2020?field:businessName={Name}&field:businessAddress={Address}&field:businessCity={City} Arcade expression: replace($feature.Name,"'",'%27') Updated URLs (attribute values encoded using an expression): https://survey123.arcgis.com/share/dd4b8079b72e480ca429824e2020?field:businessName={expression/expr1}&field:businessAddress={Address}&field:businessCity={City}   If you have multiple fields containing values with apostrophes that you need to pass as URL parameters to Survey123, you need to add a expression for each field. If you are using the custom URL scheme only to launch Survey123 from Map Viewer, you cannot use this workflow since it will not give you the expected results. Map Viewer automatically encodes URLs so it replaces % in %27 (from the Arcade expression results) with "%25". As a result, it does not pass the expected values to the questions (e.g. "Amelia%27s French Bakery"). This workflow must be used only if the custom URL scheme is being utilized in mobile apps like Field Maps where the app reads the encoded values and passed the correct values to the survey form as expected (e.g. "Amelia's French Bakery").   Best, MJ ... View more

@bgomes thanks for the update! I'm glad that we were able to reproduce the same behavior in field app.  We are currently discussing this behavior internally to confirm what is the expected behavior in both field app and web app with both constraint formats and log a defect if needed.  Please let me know if you run into any issues moving forward or if you have any other questions.  Best, MJ ... View more

@bgomes Both constraints should work in Survey123 field app (and Connect) as well. The only difference is that while web app validates the responses against the constraints as soon as input (in this case images) are provided, the field app only imposes the constraints upon submitting the form. Therefore, field app allows adding more images than what is specified in the constraint since the image question has multiline appearance, however, it does not allow user to submit the form.      ... View more

Hi @bgomes,  Can you confirm what version of Survey123 Connect you are using? I cannot reproduce the issue on 3.13.251. If you have published your survey from an older version, make sure to turn off the version lock to force using the 3.13 web app. Images below show my XLS form and the same survey in web form. Please let me know if you still experience the same issue.  Thanks, MJ     ... View more