Select to view content in your preferred language

ArcGIS Enterprise 10.9 Web AppBuilder Screening Widget shapefile export returns /webappviewer/null

227
1
3 weeks ago
Labels (1)
KabirAhmad
New Contributor

ArcGIS Enterprise 10.9 Web AppBuilder Screening Widget shapefile export returns /webappviewer/null

I am using the Web AppBuilder Screening widget in ArcGIS Enterprise 10.9. The screening analysis runs successfully, but when I click the shapefile download/export option, the browser redirects to:

/arcgis/apps/webappviewer/null

and returns 404.

Testing completed:

  • All layer REST URLs load correctly
  • Query capability is enabled
  • Screening analysis works
  • ExtractDataTask GP service tested directly through REST
  • GP job returns esriJobSucceeded
  • Output parameter is GPDataFile
  • REST output returns a valid ZIP URL
  • ZIP downloads successfully when opened directly

Example GP output:

{
  "paramName": "Output_Zip_File",
  "dataType": "GPDataFile",
  "value": {
    "url": "https://<server>/arcgis/rest/directories/arcgisjobs/.../scratch/AreaofInterest.zip"
  }
}

However, the Screening widget UI still tries to open /webappviewer/null.

Has anyone seen this in Enterprise 10.9? Is this a known Screening widget issue, config corruption, or Portal/WebContextURL issue?

0 Kudos
1 Reply
martinalexandros
Emerging Contributor

Since the GP service completes successfully and returns a valid GPDataFile URL, the issue is unlikely to be with ExtractDataTask itself. The fact that the widget redirects to /webappviewer/null suggests the Screening widget is failing to parse the returned download URL and is passing a null value to the download handler. This may be a known limitation/bug in Enterprise 10.9 Web AppBuilder Screening Widget. I would verify the Portal WebContextURL configuration, test with a newly created Web AppBuilder application, and if possible compare behavior in 10.9.1 or later versions. Since the ZIP file downloads correctly from the REST endpoint, the problem appears to be within the widget client-side logic rather than the GP service.

0 Kudos