AddFeatures failing after upgrade

Dan Giersz

16. September 2015 21:10

Hello,

After upgrading GE to 4.4 and GVH to 2.5, our workflow that adds a new feature is failing at the AddFeature task.

The workflow takes an address in a form, geocodes it, creates a graphic from the geocode results and adds a couple attributes, then converts the graphic to a featureset that is used in the AddFeatures task.

It keeps failing on the AddFeature task and I am not sure why.  I modified the workflow to create a spreadsheet from the featureset to make sure there was data there and it gave me a spreadsheet with a record.

I just get Error: Unhandled exception: 'Unable to complete operation.' in activity '1.20: AddFeatures'.

 

  Unable to complete operation.

This worked fine before the upgrade so it's very frustrating.

Any ideas?

Thanks,

Dan

 

0

• 

  Stefan Schweigert

  16. September 2015 23:17

  Hello Dan,

  I've tested this activity with the GE 4.4 release and it was working correctly for me. There were no changes made to this activity between 4.3 and 4.4; was this the previous version you were using?

   

  Also, do you happen to have a version of the workflow before you made the upgrade, to make sure that nothing changed in the workflow prior to the upgrade?

   

  Thanks, Stefan

  0
• 

  Dan Giersz

  16. September 2015 23:34

  Hi Stefan,

   

  Yes, we were using GE 4.3 and GVH 2.4 when it worked last. I just upgraded to GE 4.4 and GVH 2.5 on Monday (9/14/2015) and was told that is when the workflow stopped working.  There are features created from 9/11/2015, but none since.

   

  I have not touched that workflow since I implemented it in July and it has worked fine until recently.  I went back and tried my local copy of the workflow and recieved the same error at the AddFeatures activity.

   

  I just opened a support case for this, as this is an important workflow for our maintenance crews.

  -Dan

  0
• 

  Dan Giersz

  28. September 2015 16:34

  There was a texbox in a form that was set to be invisible (so the end user could not change its value).  The value of the text box was used further down the workflow (Probably should have used a combobox with only one entry, as suggested by tech support, or just assigned the value to a variable).  It was also a required field for the feature service.  The upgrade to GE 4.4 caused the value to be invisible to the entire workflow, not just to the end user using the form.  No value for a required field caused the AddFeature command to fail.

   

  Making the texbox visible in the form corrected the issue.

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.