topic Re: Javascript API: applyEdits - when does the globalID get created? in ArcGIS JavaScript Maps SDK Questions

Javascript API: applyEdits - when does the globalID get created?

BatesRambow — Wed, 27 Jul 2016 18:53:02 GMT

Javascript API Version 3.16

I have an issue with the applyEdits method on a Feature Layer when creating new features. I'm trying to get the GlobalID that is automatically generated. The REST response shows that the globalID did successfully get created but my attempts to get it via javascript keep resulting in 'undefined'. I'm wondering if there's a timing issue with when the globalID actually gets created?

I've tried this with two approaches, neither successful:

First approach

app.projectLayer.applyEdits([projectPoly], null, null).then(function(response) {

      app.map.graphics.remove(projectPoly);
      app.projectLayer.refresh();
    });

app.projectLayer.on('edits-complete', function(result){

var projectObjId = result.adds[0].objectId;

var projects = app.projectLayer.graphics;

for (var i = 0, len = projects.length; i < len; i++) {

console.log(projects.attributes.GlobalID);

}

Second approach

    app.projectLayer.applyEdits([projectPoly], null, null).then(function(response) {
      var projectObjId = response[0].objectId;
      var projects = app.projectLayer.graphics;
      for (var i = 0, len = projects.length; i < len; i++) {
        if(projects.attributes.OBJECTID == projectObjId){
          console.log(projects.attributes.GlobalID);
        }
      }
      app.map.graphics.remove(projectPoly);
      app.projectLayer.refresh();

});

In both of these cases the console.log statement returns undefined. However if i set it to console.log(projects[i-1].attributes.GlobalID);, I get the GlobalID of the next-to-last feature, as expected. Why is it returning undefined for the newly created feature, especially when the REST response shows that the GlobalID was successfully created?

Re: Javascript API: applyEdits - when does the globalID get created?

EvelynHernandez — Wed, 27 Jul 2016 19:12:53 GMT

Remember the fields are case sensitive. I think objectId has to be uppercase to get the value.

Try it and see if it was the issue.

Re: Javascript API: applyEdits - when does the globalID get created?

BatesRambow — Wed, 27 Jul 2016 19:18:58 GMT

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

Re: Javascript API: applyEdits - when does the globalID get created?

EvelynHernandez — Wed, 27 Jul 2016 20:04:38 GMT

app.projectLayer.on('edits-complete', function(result){

var projectObjId = result.adds[0].objectId;

var projects = app.projectLayer.graphics;

for (var i = 0, len = projects.length; i < len; i++) {

console.log(projects.attributes.GlobalID);

}

can u tell me what u get in the result from edits-complete?

I just know it will be an array, but i wanna know the structure of it.

I read in somewhere that maybe for accessing the objectid u need to do something like: results.adds.attributes.objectId

Re: Javascript API: applyEdits - when does the globalID get created?

BatesRambow — Thu, 28 Jul 2016 13:33:16 GMT

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?

Re: Javascript API: applyEdits - when does the globalID get created?

EvelynHernandez — Thu, 28 Jul 2016 13:39:00 GMT

Can u tell me what u get after this line? Cuz i think u are not getting what u want for a "project" (globalid and object,right?)

app.projectLayer.applyEdits([projectPoly], null, null).then(function(response) {

//here <--

...

}

Re: Javascript API: applyEdits - when does the globalID get created?

BatesRambow — Thu, 28 Jul 2016 13:49:15 GMT

This is what is returned after applyEdits:

Re: Javascript API: applyEdits - when does the globalID get created?

EvelynHernandez — Thu, 28 Jul 2016 13:51:49 GMT

So, u dont need the objectID, u need the global, right?

Cuz to getting the objectid generated for the last project u must do something like:

var myOBJID = response[0].objectId; //4410

Can u open functions to see what u get?

Re: Javascript API: applyEdits - when does the globalID get created?

BatesRambow — Thu, 28 Jul 2016 13:56:35 GMT

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.

Re: Javascript API: applyEdits - when does the globalID get created?

EvelynHernandez — Thu, 28 Jul 2016 14:15:32 GMT

OK now i understand.

Yea, i think when u do an applyedits, u need to wait till it get done, so u need to do callbacks o promises to handle the asyn issue.

So making a summary, u need to do:

After applyedits ends, rescue the objectid for the new object generated by the service.

After that, compare the objectid with the one u have already in the projects layer ( cuz it has to be updated already)

And then u get the globalid field.

I understand the flow like this, tell me if im wrong.

I could do something like this to resolve the problem:

function doAppEdits(projectPoly,callback){

app.proyectLayer.applyEdits([projectPoly],null,null).then((response)=>{

if (response[0].objectId){

callback(response[0].objectId);

return;

}

callback("NONE");

});

}

//here u will get the objectid number or "NONE" if doesnt exist.

var doneApplyEdits = doAppEdits(pp, (callback)=>{

//compare the array of project that u have with the objid that u already generated here

// if the layer is not refreshed maybe u will have to refresh it by force. I know there is a function to do that but i dont remember how was it.

var projectGlobalID = app.projectLayer.graphics.map(project =>{

if(project.attributes.OBJECTID == callback){

return project.attributes.GlobalID;

}

});

console.log("my global id for this project is:", projectGlobalID);

});

Re: Javascript API: applyEdits - when does the globalID get created?

BatesRambow — Thu, 28 Jul 2016 14:51:08 GMT

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.

Re: Javascript API: applyEdits - when does the globalID get created?

KellyHutchins — Thu, 28 Jul 2016 17:42:45 GMT

Here's an example showing how to get the attributes for the newly created feature. Is this what you are trying to accomplish?

JS Bin - Collaborative JavaScript Debugging

Re: Javascript API: applyEdits - when does the globalID get created?

BatesRambow — Thu, 28 Jul 2016 18:03:27 GMT

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.

Re: Javascript API: applyEdits - when does the globalID get created?

KellyHutchins — Thu, 28 Jul 2016 18:20:04 GMT

I don't have a test service with globalId enabled to verify but does the globalId ever show up in your attributes when queried via the JSAPI. For example if we leave editing out of the picture and you just query your feature layer for all the features is the globalID attribute returned?

Re: Javascript API: applyEdits - when does the globalID get created?

BatesRambow — Thu, 28 Jul 2016 18:24:33 GMT

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.

Re: Javascript API: applyEdits - when does the globalID get created?

BatesRambow — Thu, 28 Jul 2016 22:31:07 GMT

Well, I figured my problem out. Instead of doing things on the 'edits-complete' event, I used the 'updates-end' event and made sure to refresh the layer so the update event would trigger. This gives me the access to the GlobalID I needed. In the end it was a pretty easy fix, I just needed a better understanding of the events available on FeatureLayer. Thanks to all for the help!

Re: Javascript API: applyEdits - when does the globalID get created?

EvelynHernandez — Thu, 28 Jul 2016 22:45:10 GMT

We were close, haha.

Good