|
POST
|
Survey123 is still logging our users out approximately on a weekly basis I've heard. When this happens, the username field is not populated and users can't submit their surveys because its a required field. As a workaround, I have a text input appear when the username is not present. My survey looks like this: type name label calculation relevant Explanation text inspector Inspector ${username} ${username} = '' If user isn't signed in, let them enter a username so the survey still submits username username username Try and auto populate the username variable label InspectionMeta Inspection concat("Inspector: ", ${inspector}) Display the username to the user so they know they are signed in. BUT this breaks the label. Inspector is never displayed to the user.
... View more
04-29-2019
10:03 AM
|
0
|
2
|
1369
|
|
POST
|
That's a new one. Not sure why those tables would cause an issue. As a side note, I am curious, why do you add _ATTACH tables to the map service?
... View more
04-22-2019
11:42 AM
|
0
|
5
|
4018
|
|
POST
|
Thanks Robert. This is the issue - we'll look into upgrading to 10.7 and use arcmap in the meantime. Thanks!
... View more
04-22-2019
09:44 AM
|
1
|
0
|
2053
|
|
POST
|
Yeah I did. The issue was if you have layers published with custom layer ID's. See my response above The underlying cause of this issue is caused in feature services published that have checked the box to "Allow assignment of unique numeric IDs for map service publishing", and have given a specific table an ID that is different than the table index. For instance, these tables might be in a web map service: - Table 1 (ID 27) - Table 2 (ID 100) ...etc.
... View more
04-22-2019
09:23 AM
|
0
|
7
|
4018
|
|
POST
|
I saw some pretty sweet demo's at the dev summit of people identifying stuff like pavement cracks from images. Are these resources available? Has anyone released any models that can be used with a collection of images? Or am I way off base here in how these things work?
... View more
04-19-2019
12:43 PM
|
0
|
1
|
1081
|
|
POST
|
Hey so I'm creating a new enterprise gdb using Pro 2.3.2. And the tool fails with this message: User has privileges required to create database objects. Geodatabase admin user already exists. Database created. Validated authorization file. User has required privileges for geodatabase setup. XML support is enabled for the database instance. You must copy the latest ST_GEOMETRY library to the PostgreSQL software location. Refer to the ArcGIS help topics for more details. Connected RDBMS instance is not setup for Esri spatial type configuration. Failed to execute (CreateEnterpriseGeodatabase). Failed at Friday, April 19, 2019 1:47:20 PM (Elapsed Time: 3.14 seconds) But the tool runs fine in ArcMap/catalog. Any tips?
... View more
04-19-2019
11:49 AM
|
0
|
2
|
2468
|
|
POST
|
I'm working on a python script to upload a sddraft xml file from ArcGIS Pro to a standalone 10.7 arcgis server that would enable the "Shared Instances" option on the service. So far, everything works, but when I enable the settings to allow shared instances, the map service throws some errors while publishing. The script modifies the xml document to set the keys to the following: provider - DMaps MinInstances - 0 MaxInstances - 0 Which is what I have found the instance JSON properties on the server get set to. Is there something else to modify in the sddraft xml file to get this working? ``` arcgisscripting.ExecuteError: ERROR 001487: Failed to update the published service with the server-side data location. Please see the server's log for more details. ERROR 001369: Failed to create the service. Failed to execute (Publish Service Definition). Failed. Failed to execute (UploadServiceDefinition). Failed to execute (PublishProMapToServer). ``` I see some other messages in the error logs: ``` 12:17:08 - Failed to rename cache folder. 12:17:08 - Error executing tool. PublishServiceDefinition Job ID: j16be642f02d74b42b63c03c41765b958 : ERROR 001487: Failed to update the published service with the server-side data location. Please see the server's log for more details. ERROR 001369: Failed to create the service. Failed to execute (Publish Service Definition). 12:17:08 - Failed to create the service.: Invalid at the top level of the document. 12:17:08 - Service rename is complete. ```
... View more
04-19-2019
10:40 AM
|
0
|
2
|
1992
|
|
POST
|
Yeah, I did find out the cause of the issue - It looks like I had an old portal referenced in Arc Pro. I had forgotten about it and had not removed it and so this call was trying to contact the portal and get these categories even though the portal didn't exist anymore. I'm glad the devs are putting a fix in to the hanging though I could see the issue coming up with any slow connection to a portal as it does hang the main thread. Thanks Kory!
... View more
04-19-2019
05:10 AM
|
1
|
0
|
1779
|
|
POST
|
Every time I open pro - it hangs on the task GetPortalsLivingAtlasCategories for about 2-3 minutes before I can do anything. I don't have any maps open, I don't have anything open in fact, other than the catelog when this happens. Is there any way to disable this or prevent it from running unless its needed?
... View more
04-17-2019
11:50 AM
|
0
|
5
|
1858
|
|
POST
|
Good morning. I'm troubleshooting a slow webmap popup request. The popup is occurring on a feature layer. Each time the pointer is clicked, this particular layer spawns 4 different http requests, which appears to be the cause of the delay. Anyone know more about this and how arcade impacts these requests? I have an arcade expression, that does a simple intersect lookup, but I'm seeing a lot of repeat requests. The arcade looks like this: ``` var neighborhoods = Intersects($feature, FeatureSetByName($datastore,"Neighborhoods")); return First(neighborhoods)['name']; ``` But the requests I'm seeing in the browser EVERY click are: 1. `.../MapServer?f=json` (root map server) 2. `.../MapServer/9/query?f=json&objectIds....etc` (this is the identify layer) 3. `.../MapServer/11?f=json` (this is the intersecting layer - repeated request) 4. .../MapServer/11/query?f=json&geometry...etc` I guess my questions are, why do 1 and 3 have to occur every time? These are completely duplicated requests. Also, in this particular web app, I'm using feature layers and layer views in 4.x, couldn't these be queried instead of the rest endpoint to achieve a more performant query result? I'm already doing this, but arcade appears to be querying the endpoint anyways and I'm not sure if there's a workaround.
... View more
04-01-2019
05:15 AM
|
0
|
1
|
1700
|
|
POST
|
Anyone know what causes this? I'm setting the panel content to some html and am getting funky looking square boxes instead of the normal menu icon. Upon inspecting the html for the layer list item it looks like: <span class="esri-icon-default-action"></span> This particular layer list is rendering a layer list for one map image layer.
... View more
03-27-2019
03:19 PM
|
0
|
2
|
1672
|
|
POST
|
Is there a way in the python tools to publish to arcgis server from Pro and enable overwrite? I've already tried setting arcpy.env.overwriteOutput = True but this still throws an error about the item existing.
... View more
03-27-2019
02:58 PM
|
0
|
0
|
742
|
|
POST
|
Hey Johnathan Hasthorpe, cc James Tedrick I've actually found the true source of this issue. My original diagnosis was incorrect. The underlying cause of this issue is caused in feature services published that have checked the box to "Allow assignment of unique numeric IDs for map service publishing", and have given a specific table an ID that is different than the table index. For instance, these tables might be in a web map service: - Table 1 (ID 27) - Table 2 (ID 100) ...etc. We do this to avoid having issues down the road where ID's might change. So often, the index of the layer doesn't match the layer id. Survey123 has this function in XFormFeatureService.qml (line 1011): function addLayerInfo(layerInfo) {
layerInfo.drawingInfo = undefined;
layerInfo.templates = undefined;
layerInfo.indexes = undefined;
for (var i = 0; i < layerInfo.fields.length; i++) {
layerInfo.fields[i].domain = undefined;
}
layerInfo.parentRelationships = [];
layerInfo.childRelationships = [];
console.log("Feature layerInfo:", JSON.stringify(layerInfo, undefined, 2));
// HERE IS where THE BUG is created.
// IF layerInfo.id is equal to some assigned integer, like 300
// and is different from the index (i) the function at 1180 will fail
layerInfos[layerInfo.id] = layerInfo;
return layerInfo;
} This will cause the function that looks up relationships to FAIL: Line 1180 (and other places!): for (var i = 0; i < layerInfos.length; i++) {
var layerInfo = layerInfos[i];
// layerInfo is null here due to the above code
console.log("Updating relationship for:", layerInfo.name);
updateChildRelationship(layerInfo);
} Does that make sense?
... View more
03-18-2019
11:14 AM
|
0
|
9
|
4018
|
|
POST
|
I'm running into an issue submitting a survey from the Windows survey123 app. The FeatureService powering the survey is a ArcGIS Server service that has been added to arcgis online. The logfiles and the hanging message show that the error occurs on a layer that doesn't even participate in the survey. The relevant error message shows: <15>1 2019-03-11T18:17:20Z WSBLT-683 Survey123forArcGIS 14156 - [AppStudio@11205 category="qml" function="getNext" filename="XFormFeatureService.qml" line="994"] qml: Requesting layerInfo: https://utility.arcgis.com/usrsvcs/servers/.../pipeline_inspections/FeatureServer/28
<15>1 2019-03-11T18:17:20Z WSBLT-683 Survey123forArcGIS 14156 - [AppStudio@11205 category="qml" function="addLayerInfo" filename="XFormFeatureService.qml" line="1022"] qml: Feature layerInfo: {
"advancedQueryCapabilities": {
"supportsDistinct": true,
"supportsOrderBy": true,
"supportsPagination": true,
"supportsQueryWithDistance": true,
"supportsReturningQueryExtent": true,
"supportsSqlExpression": true,
"supportsStatistics": true,
"supportsTrueCurve": true
},
"archivingInfo": {
"startArchivingMoment": 1551457550000,
"supportsQueryWithHistoricMoment": true
},
"capabilities": "Create,Query,Update,Delete,Uploads,Editing",
"copyrightText": "",
"currentVersion": 10.51,
"dateFieldsTimeReference": {
"respectsDaylightSaving": false,
"timeZone": "UTC"
},
"description": "",
"displayField": "contractorname",
"editFieldsInfo": null,
"fields": [
{
"alias": "objectid",
"editable": false,
"name": "objectid",
"nullable": false,
"type": "esriFieldTypeOID"
},
{
"alias": "Service Type",
"editable": true,
"length": 255,
"name": "servicetype",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Any route obstructions",
"editable": true,
"length": 255,
"name": "routeobstruct",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Locates Marked",
"editable": true,
"length": 255,
"name": "locatemarked",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Electric Meter installed",
"editable": true,
"length": 255,
"name": "electricmeter",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Gas Meter Location marked",
"editable": true,
"length": 255,
"name": "gasmetermarked",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Site is to grade",
"editable": true,
"length": 255,
"name": "sitegrade",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Sewer Cleared",
"editable": true,
"length": 255,
"name": "sewerclear",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Route flagged",
"editable": true,
"length": 255,
"name": "routeflag",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Contractor name",
"editable": true,
"length": 255,
"name": "contractorname",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Backbone service",
"editable": true,
"length": 255,
"name": "backboneservice",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Inservice date",
"editable": true,
"length": 8,
"name": "inservicedate",
"nullable": true,
"type": "esriFieldTypeDate"
},
{
"alias": "Completion date",
"editable": true,
"length": 255,
"name": "completiondate",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Gas Workorder Number",
"editable": true,
"length": 255,
"name": "gasworknumber",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Electric Workorder Number",
"editable": true,
"length": 255,
"name": "electricworknumber",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "Main workorder number",
"editable": true,
"length": 255,
"name": "mainworknumber",
"nullable": true,
"type": "esriFieldTypeString"
},
{
"alias": "globalid",
"editable": false,
"length": 38,
"name": "globalid",
"nullable": false,
"type": "esriFieldTypeGlobalID"
},
{
"alias": "Site Check ID",
"editable": true,
"length": 38,
"name": "sitecheckglobalid_service",
"nullable": true,
"type": "esriFieldTypeGUID"
}
],
"globalIdField": "globalid",
"hasAttachments": false,
"htmlPopupType": "esriServerHTMLPopupTypeNone",
"id": 28,
"isDataVersioned": false,
"maxRecordCount": 1000,
"name": "NewService",
"objectIdField": "objectid",
"ownershipBasedAccessControlForFeatures": null,
"relationships": [],
"subtypeField": "",
"supportedQueryFormats": "JSON, AMF, geoJSON",
"supportsAdvancedQueries": true,
"supportsApplyEditsWithGlobalIds": true,
"supportsCalculate": false,
"supportsRollbackOnFailureParameter": true,
"supportsStatistics": true,
"supportsValidateSQL": true,
"syncCanReturnChanges": true,
"type": "Table",
"typeIdField": "",
"types": [],
"useStandardizedQueries": true,
"parentRelationships": [],
"childRelationships": []
}
<15>1 2019-03-11T18:17:20Z WSBLT-683 Survey123forArcGIS 14156 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: Inspection
<12>1 2019-03-11T18:17:20Z WSBLT-683 Survey123forArcGIS 14156 - [AppStudio@11205 category="default" filename="XFormFeatureService.qml" line="1180"] qrc:/qml/XForms/XFormFeatureService.qml:1180: TypeError: Cannot read property 'name' of undefined
<15>1 2019-03-11T18:17:22Z WSBLT-683 Survey123forArcGIS 14156 - [AppStudio@11205 category="qml" function="expression for onStateChanged" filename="Portal.qml" Looks like the relevant line in survey123 is: Update: I did a little more digging and found a different version of survey123 that shows the error. Looks like the issue is caused when there is a table that participates in a relationship with another layer in the feature service in the table, but does not participate in a relationship with the main layer. cc James Tedrick function updateRelationships() {
function updateChildRelationship(childLayerInfo) {
if (XFormJS.isNullOrUndefined(childLayerInfo.relationships)) {
return;
}
var childRelationship;
for (var i = 0; i < childLayerInfo.relationships.length; i++) {
var relationship = childLayerInfo.relationships[i];
if (relationship.cardinality === "esriRelCardinalityOneToMany" &&
relationship.role === "esriRelRoleDestination") {
childRelationship = relationship;
break;
}
}
if (!childRelationship) {
return;
}
var childKeyField = findField(childLayerInfo, childRelationship.keyField);
if (!childKeyField) {
console.error("Child keyField not found:", childRelationship.keyField);
return;
}
if (childKeyField.type !== "esriFieldTypeGUID") {
console.error("Unsupported childKeyField type:", childKeyField.type);
return;
}
childRelationship.keyFieldInfo = childKeyField;
var parentLayerInfo = layerInfos[childRelationship.relatedTableId];
if (!parentLayerInfo) {
return;
}
var parentRelationship;
for (i = 0; i < parentLayerInfo.relationships.length; i++) {
relationship = parentLayerInfo.relationships[i];
if (relationship.id === childRelationship.id) {
if (relationship.cardinality === "esriRelCardinalityOneToMany" &&
relationship.role === "esriRelRoleOrigin") {
parentRelationship = relationship;
console.log("relationship:", parentRelationship.id, parentRelationship.name, "<==>", childRelationship.name);
break;
} else {
return;
}
}
}
if (!parentRelationship) {
return;
}
var parentKeyField = findField(parentLayerInfo, parentRelationship.keyField);
if (!parentKeyField) {
console.error("Parent keyField not found:", parentRelationship.keyField);
return;
}
if (parentKeyField.type !== "esriFieldTypeGUID" && parentKeyField.type !== "esriFieldTypeGlobalID") {
console.error("Unsupported parentKeyField type:", parentKeyField.type);
return;
}
if (parentKeyField.type === "esriFieldTypeGlobalID" && !featureServiceInfo.supportsApplyEditsWithGlobalIds) {
console.error("Feature service requires supportsApplyEditsWithGlobalIds for parent keyField type:", parentKeyField.type);
return;
}
parentRelationship.keyFieldInfo = parentKeyField;
console.log("child name:", childLayerInfo.name, "childRelationship:", JSON.stringify(childRelationship, undefined, 2));
console.log("parent name:", parentLayerInfo.name, "parentRelationship:", JSON.stringify(parentRelationship, undefined, 2));
childLayerInfo.parentRelationships[parentLayerInfo.name] = childRelationship;
parentLayerInfo.childRelationships[childLayerInfo.name] = parentRelationship;
if (parentKeyField.type === "esriFieldTypeGlobalID") {
useGlobalIds = true;
}
return true;
}
for (var i = 0; i < layerInfos.length; i++) {
var layerInfo = layerInfos[i];
console.log("Updating relationship for:", layerInfo.name);
updateChildRelationship(layerInfo);
}
return true;
}
... View more
03-11-2019
01:44 PM
|
0
|
11
|
5207
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 05-30-2019 07:30 AM | |
| 1 | 02-21-2022 01:09 PM | |
| 2 | 12-07-2021 11:51 AM | |
| 1 | 08-18-2016 01:47 PM | |
| 1 | 10-02-2015 07:32 AM |
| Online Status |
Offline
|
| Date Last Visited |
06-28-2022
12:44 PM
|