Moving from a solution in AGOL to Portal

[Laura]

I was just wondering if anyone has started with a solution in AGOL and then went and launched that solution in Portal when it became available. Is this manageable? I would like to deploy the new cemetery management solution in AGOL, but ultimately would prefer this in Portal.. I just like the idea of waiting for the built out solution. 

[DanielWickens · Accepted solution]

@ToddPlank2's recommendation is correct. We are planning to release a version of Cemetery Management at Enterprise 11.2. The feature layers and schema will not change, so you will be able to export your data from your AGOL solution and load it into the Enterprise version.

A more complicated option is to re-create the solution's maps, apps, and views in ArcGIS Enterprise, either manually or with the help of ArcGIS Assistant. However, if you're okay with waiting for the solution to be available at Enterprise 11.2, that will be the best option.

[Lacy_House]

Trying to deploy Address Management Solution in 11.2; however, will start to build and then fails with the error "failure to deploy solution." On inspect can see where all the components are attempting to deploy then failure. See error in image. 

[ChrisFox]

@Lacy_House, all the items that are referenced there in the error are Feature Services included in the solution. Could you try something to test if there is an issue with deploying hosted feature services in the portal?

1. From the Content page in your portal, click New Item
2. Click Feature Layer > Use a Template
3. Select the AEDs and then Next through all the other dialogs to create the service.

Does it successfully create?

[Lacy_House]

Completely missing the option to create a new (Feature Layer).

[ChrisFox]

It appears either your user account or Enterprise portal doesn't have the necessary prerequisites to publish hosted layers. See the documentation below for more information:

https://enterprise.arcgis.com/en/portal/latest/use/hosted-web-layers.htm

Most solutions include hosted feature layers which require this functionality be available in the portal in order to deploy solutions. If you enable this ability you should no longer see this error when deploying.