Zum Hauptinhalt gehen

GPDataFile with Create Temp File activity

Kommentare

4 Kommentare

  • Permanently deleted user
    Hi Ricardo,

     

    I'm not 100% sure on this, but I think the geoprocessing inputs that accept a web request do not handle web addresses that have URL parameters (e.g. our GUID and contentType parameters).  I have observed this behavior but I do not have any documentation confirming it.

     

    If you can republish the geoprocessor, then you could call it directly with a Feature parameter rather than a file path.

     

    Otherwise, you may be able to use Workflow to download the file and copy it to a web-hosted folder that would let you use an absolute URL with no parameters for your geoprocessor.

     

    Regards,

     

    -Malcolm
    0
  • Permanently deleted user
    HI Ricardo,

     

    I'm having the exactly same issue with try to upload a file for GPService. Could you please explain a bit more what you mean by "call it directly with a Feature parameter rather than a file path"? How I do this with a DWG file? Also I've enabled the Upload capability to the GPService and upload the DWG file to AGS and got a return itemID. According to AGS doc it's possible to use GPItemID to replace GPDataFile. However, I couldn't find a way in the Geoprocessor activity to use GPItemID. any thoughts? thanks.
    0
  • Permanently deleted user
    Hi Jack, had the same issue and ended up modifying the XAML outside the Workflow Designer, replacing GPDataFile with GPDataItem. Cheers, Hen
    0
  • Permanently deleted user
    Thanks Hen for the tip. In my case I ended up replace %2F to / in the file URL and that works. also make sure you have "applicaiton/.dwg" for the content type
    0

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