KB-1279 "We cannot have any import failures" error thrown in the application server log after attempting to create a Quick App

Parmida Borhani — Thu, 09 Aug 2018 02:16:05 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 8/9/2018 2:16:05 AM

Symptoms

When attempting to create a Quick App, the following error message is returned:

Quick App Not Created - Oops! Something wen wrong and we couldn't create your Quick App. Nothing has currently been created. 
You can try to create your Quick App again, but if it continues failing please contact a system administrator.

In the application server log, the following error can be seen:

ERROR com.appiancorp.object.quickapps.QuickAppObjectType - Failure importing object:
...
cause=com.appiancorp.ix.binding.UnresolvedReferencesException: type=content, unresolvedSrcIds=[UUID]
...
ERROR com.appiancorp.object.quickapps.QuickAppObjectType - Failed to create a new quick app
java.lang.IllegalStateException: We cannot have any import failures

Cause

When creating a Quick App, system objects are imported from the Appian installation. The error is seen when the name of one of the system objects imported conflicts with one of the existing objects in the Appian designer. This results in an import failure, and ultimately prevents the creation of the Quick App.

Action

Locate the conflict by using the UUID provided in the error description. Once the name of the conflicting object is found, rename it and recreate the Quick App.

In order to locate the object, one can find it manually in the /designer interface or use the Content Details By UUID shared component.
Export the object from the system.
Delete the object from the system.

Modify the name of the exported object using the downloaded XML file to something else. An example is shown below:

XML snippet before changes:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<contentHaul xmlns:a="http://www.appian.com/ae/types/2009">
    <rule>
        <name>test_KB1279</name>
        <uuid>_a-0001dcff-f301-8000-9ba2-011c48011c48_42670</uuid> 
...

XML snippet after changing the name:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<contentHaul xmlns:a="http://www.appian.com/ae/types/2009">
    <rule>
        <name>test_KB1279_name_change</name>
        <uuid>_a-0001dcff-f301-8000-9ba2-011c48011c48_42670</uuid> 
...

Re-import the object with the changed name.

Affected Versions

This article applies to Appian 16.2 and later.

Last Reviewed: April 2018

Tags: application design, Quick Apps

KB-1279 "We cannot have any import failures" error thrown in the application server log after attempting to create a Quick App

Parmida Borhani — Wed, 04 Apr 2018 03:29:17 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 4/4/2018 3:29:17 AM

Symptoms

When attempting to create a Quick App, the following error message is returned:

Quick App Not Created - Oops! Something wen wrong and we couldn't create your Quick App. Nothing has currently been created. 
You can try to create your Quick App again, but if it continues failing please contact a system administrator.

In the application server log, the following error can be seen:

ERROR com.appiancorp.object.quickapps.QuickAppObjectType - Failure importing object:
...
cause=com.appiancorp.ix.binding.UnresolvedReferencesException: type=content, unresolvedSrcIds=[UUID]
...
ERROR com.appiancorp.object.quickapps.QuickAppObjectType - Failed to create a new quick app
java.lang.IllegalStateException: We cannot have any import failures

Cause

Action

Locate the conflict by using the UUID provided in the error description. Once the name of the conflicting object is found, rename it and recreate the Quick App.

In order to locate the object, one can find it manually in the /designer interface or use the Content Details By UUID shared component.
Export the object from the system.
Delete the object from the system.

Modify the name of the exported object using the downloaded XML file to something else. An example is shown below:

XML snippet before changes:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<contentHaul xmlns:a="http://www.appian.com/ae/types/2009">
    <rule>
        <name>test_KB1279</name>
        <uuid>_a-0001dcff-f301-8000-9ba2-011c48011c48_42670</uuid> 
...

XML snippet after changing the name:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<contentHaul xmlns:a="http://www.appian.com/ae/types/2009">
    <rule>
        <name>test_KB1279_name_change</name>
        <uuid>_a-0001dcff-f301-8000-9ba2-011c48011c48_42670</uuid> 
...

Re-import the object with the changed name.

Affected Versions

This article applies to Appian 16.2 and later.

Last Reviewed: April 2018

Tags: Quick Apps

KB-1279 "We cannot have any import failures" error thrown in the application server log after attempting to create a Quick App

Nick Vigilante — Tue, 07 Mar 2017 15:50:47 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 3:50:47 PM

Symptoms

When attempting to create a Quick App, the following error message is returned:

Quick App Not Created - Oops! Something wen wrong and we couldn't create your Quick App. Nothing has currently been created. 
You can try to create your Quick App again, but if it continues failing please contact a system administrator.

In the application server log, the following error can be seen:

ERROR com.appiancorp.object.quickapps.QuickAppObjectType - Failure importing object:
...
cause=com.appiancorp.ix.binding.UnresolvedReferencesException: type=content, unresolvedSrcIds=[UUID]
...
ERROR com.appiancorp.object.quickapps.QuickAppObjectType - Failed to create a new quick app
java.lang.IllegalStateException: We cannot have any import failures

Cause

Action

Locate the conflict by using the UUID provided in the error description. Once the name of the conflicting object is found, remove or rename it, and recreate the Quick App.

Notes:

In order to locate the object, one can find it manually in the /designer interface or use the Content Details By UUID shared component.

In order to successfully rename the object:

Export the object and remove the rule from the system.

Modify the name in the XML file to something else. An example is shown below:
XML snippet before changes:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<contentHaul xmlns:a="http://www.appian.com/ae/types/2009">
    <rule>
        <name>test_KB1279</name>
        <uuid>_a-0001dcff-f301-8000-9ba2-011c48011c48_42670</uuid> 
...

XML snippet after changing the name:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<contentHaul xmlns:a="http://www.appian.com/ae/types/2009">
    <rule>
        <name>test_KB1279_name_change</name>
        <uuid>_a-0001dcff-f301-8000-9ba2-011c48011c48_42670</uuid> 
...

Affected Versions

This article applies to Appian 16.2 and later.

Last Reviewed: March 2017

Tags: Quick Apps