Custom widget - DWG export

Saulo

I'm developing a widget to expert a feature services from an Experience Builder app to DWG.

I wrote a Python toolbox, but the error below is occuring:

line 113, in execute
    arcpy.analysis.Clip(
    ~~~~~~~~~~~~~~~~~~~^
        layer,
        ^^^^^^
        area_analise,
        ^^^^^^^^^^^^^
        output_fc
        ^^^^^^^^^
    )
    ^
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\__init__.py", line 2782, in wrapped
    result = fn(*args, **kwargs)
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\analysis.py", line 202, in Clip
    raise e
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\analysis.py", line 198, in Clip
    gp.Clip_analysis(*gp_fixargs((in_features, clip_features, out_feature_class, cluster_tolerance), True))
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 541, in <lambda>
    return lambda *args: val(*gp_fixargs(args, True))
                         ~~~^^^^^^^^^^^^^^^^^^^^^^^^^
arcgisscripting.ExecuteError: Failed to execute. Parameters are not valid.
ERROR 000840: The value is not a Feature Layer.
ERROR 000840: The value is not a Scene Layer.
ERROR 000840: The value is not a Building Scene Layer.
ERROR 000840: The value is not a File.
Failed to execute (Clip).



Failed to execute (ExportDWG).

Has anyone made a script like this before? My goal is to use ArcGIS Pro to build custom toolboxes, publish them as geoprocessing services on ArcGIS Enterprise, and use the Analysis widget to load this custom tool.

Thanks

MattiasEkstrom

It's possible to do that, I have a pythonscript that clips an elevation raster, converts it to points och exports them to a DWG-file. An I've published it as a geoprocessing service and using the service from a custom widget.
Your errors says that there are issues with the input parameters.
I'd start by getting a python script working in ArcGIS Pro with hard coded inputs, then convert them to parameters and finallly publishing as a geoprocessing service. If you haven't already done that.