I am trying to publish a script tool as a geoprocessing service, but there are several issues that I have run into recently has caused the tool to not execute as I originally expected.
Any help on this would be highly appreciated.
Also, I noticed that when the tool is published that the end user can select an analysis layer, but it appears as though they can only select the layer from the organization, not something that is derived. Is this something that would have to be scripted as an update tool validation in order for the end user to select the feature class?
I would suggest to set the type of the CAD file parameter to be "File", and when publishing the GP service to make sure that you check "Upload" within the capabilities configuration.
This should allow you to upload the DWG file instead of having it as a constant.
Thanks @IhabHassan for the suggestion. I will give that a try and test it to see how it performs. As for the other constant issue, I think it may have something to do with having the inputs as a table of values rather than simple input values. Is that the case or is there a way to publish the tool with a table of values as inputs rather than constants? I would greatly appreciate it if you or someone could let me know.