Experience Builder Developer Edition 1.18 Export to Shapefile, Geodatabase, or KML

[Brian_McLeer]

I am using the out of the box map layers widget in EB DE 1.18 that was released today, and I am unable to export to shapefile, file gdb, or KML from the map layers widget. Has anyone else had luck trying this? I don't get many error messages, but when I choose one of the 3 export options I get the console error below. Prior options such as CSV, JSON, and GeoJSON export as normal. 

[VenkataKondepati]

Hi Brian,

I haven’t tried the 1.18 release myself yet, but that error definitely looks like a React rendering issue — specifically with how those export formats (Shapefile, FileGDB, KML) are being handled inside the widget.

The fact that CSV, JSON, and GeoJSON still work suggests the widget’s core logic is fine, but something's missing or misconfigured for the other formats — maybe a handler wasn't properly registered or there’s a broken condition in the export component.

I’ll try to spin up a test on my end soon, but it wouldn’t surprise me if this is a regression in 1.18. You might want to raise it with Esri or check GitHub to see if others have reported it yet.

If I get a chance to test it later today, I’ll let you know what I find.

Regards,

Venkat

[Brian_McLeer]

Thank you @VenkataKondepati, I will give the Community Post a couple of days but might create an Esri ticket if needed. 

[Brian_McLeer]

@VenkataKondepati I did a little more testing and a few things of note. The issue is occurring in the Table widget as well. 

It oddly works in the Select Features widget and map pop-up, but requires an Enterprise or AGOL login. There is a community post about this. 

https://community.esri.com/t5/arcgis-experience-builder-ideas/export-shapefile-from-exb-pop-up-windo...

The query widget prompts the dialogue box, but gives an Error 99999.

[ShengdiZhang]

Hi @Brian_McLeer ,

Currently, "Export Records" uses a different method from "Export All Data". Exporting records to SHP/FGDB/KML formats requires the user to be signed in, though we are considering improvements to this feature in future releases.

"Export All" usually uses the ArcGIS REST API's createReplica operation. The error message you received suggests that there might be a bug with the createReplica request.

Could you please check the Network tab in your browser's developer tools and confirm whether a createReplica request is being made when you try to export? If so, what's the status of that request?

Thanks,

Shengdi

[VenkataKondepati]

Hi @Brian_McLeer,

Thanks for sharing the post.
We also use backend FME REST services for all export-related functionality in our browser-based applications.
We have built FME Flow jobs and exposed them through REST services. Our custom browser applications send requests to the FME Server with selected parameters, such as the layer and selection or extent, along with a few other options to export the content.
This setup has been working reliably for many years. We also perform occasional imports using a similar approach.

Regards,

Venkat

[Brian_McLeer]

Thank you @VenkataKondepati, since @ShengdiZhang mentioned that improvements are being considered to have shapefile, KML and FGDB not require an AGOL or Enterprise login in a future release, I will hold off for now with these export options.  

[Brian_McLeer]

Hi @ShengdiZhang , I am not getting any line items on the log when going to the network tab and exporting to shapefile, KML, or GDB. 

[ShengdiZhang]

Hi, can you share your data with me? My username is she10946, and I want to see if I can reproduce this bug.

Thanks,

Shengdi

[AbiDhakal]

@Brian_McLeer - Have you had any luck? Were you able to accomplish your task?

I'm also trying to do the same thing but am only able to extract CSV file and not a shape file. You response in this matter would really help.

Thank you,
Abi