Latest Contributions by BatesRambow

You are getting it on the same group ID we are - an esri created group for ArcGIS Online vector basemaps. Makes me think that ESRI's servers hosting those basemaps are the source of the CORS problems, not our portals. Seems like that may be the legacy vector basemaps as well, although I don't think it's due to anything we have configured. Update: The failing request also fails with cURL, which would not be affected by CORS. ... View more

Some more insight into our issue. As others have mentioned, the console shows a CORS error but our CORS settings are completely open. Also if you watch the network traffic while attempting to open a survey detail page, you can see many successful requests and a single failed request. CORS issues wouldn't allow some requests to succeed and others fail in this manner. I dug into the failed request. It's the `/search` endpoint searching for the ArcGIS Online Vector Basemap group, as its url exists via our Portal: Wondering what other people are seeing in their network traffic. ... View more

Same issue here. Republishing the surveys does not help. Console shows CORS errors, but there is nothing that has changed on our Portal end in the last 24 hours.   Also, when trying to access the item directly from Portal rather than the Survey123 site, we get a slightly different error, stating the .webform file is missing.     ... View more

Following up that this is still an issue with the Search widget, even in 4.22. Simple fix is to make sure all the buttons in the source code are correctly attributed as type=button. ... View more

I wrote a python script that will generate a simple "data dictionary" with a list of fields, aliases, types and length.  The input is a feature class and the output is a CSV file.   https://gist.github.com/brambow/120c8df8bad4a11cb6fc1859ea223cc7 ... View more

Yes, it is.  If I return an array of all the existing features in the layer, outside of an editing operation, the returned attributes include GlobalID.  This is also demonstrated in one of my posts above, where I show that the object in the 'projects' array includes the global id, but when i drill down and return a single object, after editing, the GlobalID attribute does not exist. Example, just returning the array of feature objects by returning app.projectLayer.graphics, outside of the edit operation.  Notice the inclusion of GlobalIDs At this point, my conclusion is that I either don't fully grasp the async timing of the edit operation and I need to take a different approach to ensure that what I'm trying to do occurs long after the edits are made, or there is a bug in the API. ... View more

Thanks, but I don't have a problem getting the attributes other than the GlobalID, and your example does not demonstrate this with GlobalID.  I can already get exactly what your code returns with my code above. If I run your code with my data, this is the console output: Still no GlobalID, even though the Feature Service has that field and all other existing features have GlobalIds.  Hence the question - when does the GlobalID get created? Here's the response from the REST service for this same action: {"addResults":[{"objectId":4025,"globalId":"{E4FB8847-BECB-44C9-9C24-FFF2976996E1}","success":true}],"updateResults":[],"deleteResults":[]} The GlobalID exists, so why isn't it showing up with the other attributes? If you can show me an example with GlobalID, that would be great. ... View more

Possibly on the right track here.  I am not using ES6 syntax so can't use the "=>" operator, but this is what I have:     function doAppEdits(projectPoly, callback){       app.projectLayer.applyEdits([projectPoly], null, null).then(function(response){         if(response[0].objectId){           callback(response[0].objectId);         }         callback("NONE");       });     }     var doneApplyEdits = doAppEdits(projectPoly, function(callback){       var projectGlobalID = app.projectLayer.graphics.map(function(project){         console.log(callback);         if(project.attributes.OBJECTID == callback){           return project.attributes.GlobalID;         }       });       console.log("globalID is: ", projectGlobalID);     }); Unfortunately, it's not quite there.  This is what I get in the console: I appreciate your continued interest, but I may have to move on to something else and leave this issue open for another time. ... View more

functions are the internal methods of FeatureEditResult: Right, I need the globalID, which is not a property of the FeatureEditResult.  I was trying to grab the ObjectID form the FeatureEditResult and match it to the matching ObjectID attribute in the array of projects, but now I'm seeing that the objectID seems to be changing at some point in the process.  To that end, I changed the statement to match on PROJECTID (a field I create and manage), but I'm still seeing the same behavior - a changed ObjectID and a missing GlobalID, even though they do exist in the projects array.  I feel like there's some kind of timing issue at hand, with  the asynchronous nature of the applyEdits, but I don't know how to dig any deeper. ... View more

This is what is returned after applyEdits: ... View more

I've isolated something that seems to be at issue here: In both scenarios, if I console.log(projects), I get an array of all the features in the "projects" layer.  If I explore the last object in that array, I see what I expect - the last added project's attribues, including the GlobalID: However, once inside the "for" statement, if I try to view a specific project (console.log(projects);) this is what I get: Notice a few things: 1) Several attribute fields, including GlobalID, don't show up. 2) The ObjectIDs are different, but this is supposed to be the exact same object inside the array. Any ideas what is happening here?  Why would the projects array include the object correctly, but when trying to single out that specific object, the attributes change? ... View more

Thanks but that's not the issue.  The syntax of 'objectId' is what is used in the FeatureEditResult​.  ... View more