Null values and Update Features command

Christopher Wiebke

May 11, 2018 14:35

I am using essentials workflow designer 4.9.0.60.

 

I am trying to assign a null value to particular fields.  I have confirmed that my variables do have a value of dbnull using an alert and the .gettype.name.tostring code.

 

the problem is that when just one variable is null, the update features command seems to be changing everyfield for that record to null.

 

Anyone know what is going on here?

 

Thanks,

 

Chris.

0

• 

  Christopher Wiebke

  May 11, 2018 14:45

  Update:  I am inserting the null value into an interger field, that does allow null values.

  0
• 

  Zack Robison

  May 11, 2018 16:32

  I haven't seen this before.  Did you look at the featureset just before the update command to ensure that your issue doesn't arise before the upadate activity?  I use the featureset.toJson method with an external log activity for this myself.

  0
• 

  Christopher Wiebke

  May 11, 2018 16:40

  I have not tried that.  That is a good idea. I will try that and post an update.  Thanks, Chris.

  0
• 

  Christopher Wiebke

  May 11, 2018 17:47

  Thank you for educating me about the Feature Set to JSON.  I have confirmed that the fields have the attributes that they should right before the update features command.  After the update features command is done, all the fields are null.

   

  _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=907f2000000k9zy&feoid=Body&refid=0EMf2000000fyDH"_/_img_

   

   

  0
• 

  Christopher Wiebke

  May 11, 2018 18:08

  I am getting this error on the server:

   

  _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=907f2000000kA08&feoid=Body&refid=0EMf2000000fyDM" _/_img_

  0
• 

  Zack Robison

  May 11, 2018 18:50

  Looks like the error is server side to me.  ESRI says that it expects the data to be in a different format that you're sending it, perhaps an integer?  I would check your arcgis server logs for more information on this one as they may be more verbose.

   

  Also, I haveve seen the 'd not applied' issue a few times as a projection issue too, so I'd also double check that your data is projected correctly when you go to update (though that shouldn't neccessarily be a problem).  I doubt that this is the issue presently but it may help, IDK.

  0

Please sign in to leave a comment.