|
POST
|
Hi Christina, It seems like you need to print a map for each repeat, and for object 60 which includes 83 assets as you mentioned, it will need to print 83 maps. Therefore, the print job for object 60 exceeds the time limitation of 10 min for one object. Here is the workaround for the issue, and you can print the object 60 separately using the method below: 1. In connect, create a new survey from the existing feature service - the related table containing the result of the repeat (83 assets are in this table) 2. Find this survey and go to the data page, only keep the section within the repeat in the report template 3. Use the filter to find all record for object 60, and print the report for them In the meanwhile, I encourage you to contact Esri Support to raise an enhancement issue. Our Support team will assign an official case number for your records. This number can be used to search for and subscribe to the bug on the Esri Support site. If the issue is reported by other customers it will be attached to the same case report, which helps us assess the impact of the issue and prioritize it accordingly. Thanks, Ruth
... View more
12-02-2020
01:49 AM
|
1
|
4
|
3073
|
|
POST
|
Hi all, The issue has been fixed on the Survey123 website now. Please leave a comment here if you have any issue with the fix. Thanks, Ruth
... View more
11-25-2020
01:29 AM
|
0
|
1
|
3385
|
|
POST
|
Hi Sam, The fix is now available on the production website. Please leave a comment if you have any problem with the fix. Thanks, Ruth
... View more
11-25-2020
01:27 AM
|
0
|
1
|
3671
|
|
POST
|
Hi Joel, Thanks for raising the issue here. The issue you raised has been fixed on the Survey123 website. Thanks, Ruth
... View more
11-25-2020
12:51 AM
|
0
|
0
|
1974
|
|
IDEA
|
Hi @Anneka_France , Thanks for sharing your idea here, I have logged your idea in our feature request list. I will reply to this post with any updates. Thanks, Ruth
... View more
11-22-2020
06:48 PM
|
0
|
0
|
4058
|
|
POST
|
Hi, The issue has been fixed, and the format for metadata start and end should work on the Survey123 website now. Please leave a comment if you have any problem with the fix. Thanks, Ruth
... View more
11-22-2020
06:43 PM
|
0
|
1
|
4238
|
|
POST
|
Hi Sam, Thanks a lot for the testing, the hotfix build will be released in mid-December. I will reply to this post, once the hotfix build is available on the production website. Thanks, Ruth
... View more
11-15-2020
10:01 PM
|
0
|
0
|
3715
|
|
POST
|
Hi, Thank you for raising the issue here! We have done some changes to the metadata types which include start and end, and it seems like the format support for them is not working. I will reply to this post with any update. If you remove the format for start_time and end_time, then the report can be generated without issue. I encourage you to contact Esri Support. Our Support team will assign an official bug number for your records. This number can be used to search for and subscribe to the bug on the Esri Support site. If the issue is reported by other customers it will be attached to the same bug report, which helps us assess the impact of the issue and prioritize it accordingly. Thanks, Ruth
... View more
11-13-2020
03:29 AM
|
1
|
3
|
4267
|
|
POST
|
Hi Sam, The bug BUG-000134972 has been fixed and available for testing on Survey123 BETA website (https://survey123beta.arcgis.com/). If it is possible could you please try our fix on the BETA website to see if that fix works for you? Thanks, Ruth
... View more
11-13-2020
02:31 AM
|
0
|
4
|
3754
|
|
POST
|
Hi Jürgen, You are right, normally the error msg contains more specific information; therefore, we will try to reproduce the issue and find out the cause, as well as why there is no error msg shown. If the issue occurs again, could you please reply to this post and paste a screenshot of the console and the network `add` request (in developer tool) which may contain more information. That will be really helpful for us to identify the issue. To log the issue, I encourage you to contact Esri Support. Our Support team will assign an official bug number for your records. This number can be used to search for and subscribe to the bug on the Esri Support site. If the issue is reported by other customers it will be attached to the same bug report, which helps us assess the impact of the issue and prioritize it accordingly. Thanks, Ruth
... View more
11-12-2020
09:21 PM
|
0
|
0
|
1635
|
|
POST
|
Hi, There is no existing function to do this, however, Survey123 does support the custom JS function. Here are some good resources: Blog: https://community.esri.com/t5/arcgis-survey123-blog/extending-survey123-smart-forms-with-custom-js-f... Doc: https://doc.arcgis.com/en/survey123/desktop/create-surveys/pulldatajavascript.htm (Please pay attention to the known limitations at the end of this doc) I have also attached a sample XLSform (Please change the feature layer url in the pulldata function) and a Javascript code (Please take the code and save it as .js file, then put the js. file into the scripts folder as described in the documentation). The following code can do simple overlap detection and returns the count of the existing polygons that are overlapping. function overlapDetection(geometry, token, featurelayer_url) {
// If there is no geometry input, output null
if (!geometry) {
return "Wait for input geometry.";
}
// If the survey is submitted in the webapp, convert the geometry to object
if (typeof(geometry) != "object") {
var geoArray = geometry.split(';');
geoArray.forEach(ArraytoAA);
var geoObject = {"rings": [geoArray]};
} else {
var geoObject = geometry;
}
var geoString = JSON.stringify(geoObject);
// Change the parameters in the query URL to work with different geometryType, spatialRel, etc.
// Ref: https://developers.arcgis.com/rest/services-reference/query-feature-service-layer-.htm
var url = featurelayer_url+"/query?where=1%3D1&geometry="+geoString+"&geometryType=esriGeometryPolygon&spatialRel=esriSpatialRelOverlaps&units=esriSRUnit_Meter&returnCountOnly=true&f=json";
if (token) {
url = url+"&token="+token;
}
var xhttp = new XMLHttpRequest();
xhttp.open("GET", url, false);
xhttp.send();
if (xhttp.status!==200) {
return (xhttp.status);
} else {
var responseJSON=JSON.parse(xhttp.responseText)
if (responseJSON.error) {
return JSON.stringify(responseJSON.error);
} else {
return JSON.stringify(responseJSON.count);
}
}
}
function ArraytoAA(item,index,array) {
var coord = item.split(' ').map(Number)
array[index] = coord;
} Thanks, Ruth
... View more
11-12-2020
08:05 PM
|
0
|
3
|
2669
|
|
POST
|
Hi Jürgen, Thanks for sharing here! I think this issue may occur due to the network issue or the server downtime. Could you please provide more information relates to this issue so that we can identify the cause of it? For example, how often do you see this kind of error? and how long does the error last, like a few hours or a few days? and it would be really helpful if you have a rough timeline of when it occurred recently. Thanks, Ruth
... View more
11-12-2020
12:54 AM
|
0
|
2
|
1669
|
|
POST
|
Hi Daniel, Thank you for sharing here! Could you please double-check the fieldworker view of your survey? If the "Enable editing" is disabled there, then the changes in the collaboration page will not be saved. Here is the detailed instruction: 1) GO to AGOL or your portal, 2) Search for your survey folder, 3) Find the fieldworker view, check this view settings. Here is a blog https://community.esri.com/t5/arcgis-survey123-blog/securing-data-in-public-surveys-survey123-web-designer/ba-p/898102 that explains the backend mechanism in depth which is worth reading. If this is not the case, please let me know, I will help you investigate further. Thanks a lot! Ruth
... View more
11-12-2020
12:09 AM
|
0
|
0
|
629
|
|
POST
|
Hi Martha, Thanks for the screenshot, the "This is a required question" is shown because the question is a required question. When the input does not meet the constraint, it also does not meet the required constraint, so the "This is a required question" which has a higher priority shows. One workaround method here, maybe you can set the required_mssage as well in the XLSform. Hope this works for you! Thanks, Ruth
... View more
11-07-2020
07:03 PM
|
0
|
0
|
1649
|
|
POST
|
Hi Martha, We will try to address this issue in the next few releases, and I will reply to this post with any updates. For the constraint message, did you also set the constraint_message in the XLSform? If yes, then I will need more information to identify the issue, a screenshot like the screenshot I posted above would be very helpful. Thanks, Ruth
... View more
11-06-2020
03:36 AM
|
0
|
2
|
1649
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | Wednesday | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 2 | a month ago | |
| 1 | 07-30-2025 11:24 PM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|