Skip to content

Troubleshooting providers

It is possible for an import of a portal app to fail if the target environment has:

  • Different live versions of the providers
  • A newer version of a provider that contains changes that are not backwardly compatible
  • Does not have an updated version of the provider

Error with external service

Error messages prefixed with the phrase Error with external service are responses from the endpoint, such as IFS Cloud. You need to check for the cause in IFS Cloud.

Before importing

  1. Check that the providers and versions are correct for the app you need to import.
  2. If you are planning to map the providers in the app file to the live version of each provider then make sure the correct version is live.
  3. Check the providers, such as the System provider. For example, to import a portal app you need to map to:

    • Either version 5 or later of the system provider
    • Or make version 5 of the system Provider live and then map to the live version

Mapping to the live provider version

An import may fail if the wrong provider version is live (see above).

For example, if app requires version 5 of the system provider but version 1 is the live version, then the import will fail if you map the system provider in the app file to the live version. Any actions in the app that use this provider may be missing from the imported app.

To fix this, you need to delete the app, change the live version of the provider to the correct one and re-import the app.

Finding out why an import or clone is failing

During an import or clone, you may occasionally see warning messages similar to the following:

missing_property_error

This message tells you that there is a difference between the metadata for the old and new provider versions. The provider type is named in the method, that is RecurringServiceProgram.

In this example, the app is configured to use the RecurringServiceProgram type, for example, an action gets data for a data grid or form that uses properties returned by the method in question. However, in the new provider version, the method does not return the same properties, and one or more properties might be missing. This prevents the import or clone from succeeding.

To fix this, begin by checking which properties are involved:

  1. In the original app, locate the action that uses the method named in the warning message.
  2. On the Actions page, find out where the action is used (the Usage tab).
  3. On the Events page, check the OnNotification events to find out which component or element subscribes to this action.
  4. On the Designer page, check the component or element in question, and get a list of the configured properties.

    These properties are potentially preventing the import or clone from succeeding. The next step is compare the old and new provider versions. 5. Still in the original app, in the Metadata Viewer, select the provider, find the provider type, and check the list of properties. 6. Create or open a app that uses the new version of the provider, and repeat the previous step. Look for differences between the two versions.

    Once you know what the difference is between the provider versions, you can update the app, for example update or remove the properties in question.