Zum Hauptinhalt gehen

Add attachment error in specific case. Using an iPad-Chrome and running workflow through Feature Actions context menu, attachments fail. Get the following activity error: undefined is not an object (evaluating t.content.lastEdit=r._lastEdited[i.id])

Kommentare

5 Kommentare

  • Ken Lyon

    Hi @BPG Mapping?,

     

    I'm sorry to heart this isn't working for you. Do you have a workflow that we could use to test this?

     

    Also, is this running in Geocortex Web or something else?

    0
  • Permanently deleted user

    Sorry for the delay getting back to you, Ken. We are running GVH (version 4.14.2.0). Also, one detail I failed to mention was that we're using secured services. Can you contact us via email for us to send the json file?

    0
  • Ken Lyon

    @BPG Mapping? At this point, I don't think I need anything too sensitive. Which activity is failing, for example?

    0
  • Permanently deleted user

    The "Add Attachment" is the activity failing. The same workflow is used in about 20 different viewers/sites. In the desktop version there haven't been reports of any issues. On the iPad, the workflow operates as expected until "Additional Details" has been selected (on any feature in any layer). After "Additional Details" is clicked, the workflow will fail with the error above. Refreshing the page and trying again (without clicking "Additional Details") will upload the attachment successfully.

     

    If attribute edits are included at the same time as uploading the attachment, those edits will be recorded regardless if the attachment fails to upload.

     

    Just tested on an iPhone with the same issues as well.

    0
  • Permanently deleted user

    I think we've found what was causing our issue (although not why). We were utilizing the layer input for the "Add Attachment" activity. We found that the issue resolved when we instead used the URL input for the activity. Additionally, we had to enter in the original url (not the geocortex url) for the service. Once we made these changes, our users can click "Additional Details" and not cause the workflow to fail.

     

    Hopefully this will help someone else using iPads in the field. However, if there is a way to get the Layer input working that would be helpful. Right now we have to make sure that the original url is hard coded into the workflow at some point for each layer. Thankfully, the url option is only needed for a few layers that are having attachments added using iPads.

    0

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