We are currently running in some issues with Geoprocessing Packages created with ArcGIS Pro 2.6.3. The input parameters representing features as a Feature Set are somehow misinterpreted as GPString by the Runtime Local Server.
When we create our Geoprocessing Packages with ArcMap 10.8 the packages are correctly loaded into the runtime apps and the input parameter is shown as Feature Set.
Are there any best practices regarding "Prepare your Geoprocessing Models for Runtime Apps with ArcGIS Pro"?
First issue we have seen some weeks ago:
Runtime Local Server: Input Feature Set is shown as GPString
Product Manager
Developers and Location Services
Germany and Switzerland
%20Office%20skaliert.png "Jan-Tschada"){kind=avatar}
