https://community.appian.com/discussions/f/general/7672/hi-all-i-am-trying-to-import-an-application-built-in-7-11-into-a-7-1Hi all, I am trying to import an application built in 7.11 into a 7.10 environment. I modified the MANIFEST.MF file to read 7.10.0.0. When I try and import my application I get several errors like the following: An error occurred while creating contenten-USTelligent Community 12https://community.appian.com/thread/31593?ContentTypeID=1Thu, 26 May 2016 20:28:53 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:32923b19-0be5-47ee-9b9a-cea43615fb31Myles WeberOk. Thank you.<div style="clear:both;"></div>https://community.appian.com/thread/31590?ContentTypeID=1Thu, 26 May 2016 20:22:36 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:a6c48c00-a417-4836-848c-752a9d7b6aa2daniellev628As an FYI - this has been addressed; no clients impacted and was only done in a test environment in a training class; won&#39;t be repeated (ever)<div style="clear:both;"></div>https://community.appian.com/thread/31585?ContentTypeID=1Thu, 26 May 2016 18:04:06 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:f18d47a9-d1b6-48ac-a68a-2a38988bce70Myles WeberPaul is exactly right. You have created a situation where your client&#39;s deployment will not be supported anymore. You are introducing issues which can&#39;t be undone.<div style="clear:both;"></div>https://community.appian.com/thread/31584?ContentTypeID=1Thu, 26 May 2016 17:40:01 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:007a28cd-a02e-42f1-a2b7-7b2e421e4935rachelz585Luckily, in this case, the application is heavily based on plug-ins and mostly uses Appian functions that have been in place for several versions, so I have not encountered any major problems :)<div style="clear:both;"></div>https://community.appian.com/thread/31583?ContentTypeID=1Thu, 26 May 2016 15:56:34 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:d71a1aff-2780-4887-b4d3-568c87696efePaul MayeurThere is more to import than the objects in the zip. We also edit databases (but business and internal). You are asking to cause a lot of problems by importing backwards. There is a reason we block it.<div style="clear:both;"></div>https://community.appian.com/thread/31576?ContentTypeID=1Thu, 26 May 2016 11:39:59 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:a8003fa3-f8a5-4ae1-a70c-5206d30d0292sikhivahans@chetany Thanks, that&#39;s my understanding. Personally I am not quiet comfortable with the approach but it&#39;s really good to know that it&#39;s possible with modifications in the objects or source xml.<div style="clear:both;"></div>https://community.appian.com/thread/31573?ContentTypeID=1Thu, 26 May 2016 11:31:18 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:1b06e0d3-93c3-469a-b361-ff492a12c526chetany@sikhivahans, If you are importing to older version of Appian, and you have used few functions/Appian functionality in your application which are not present in the old version, you need to remove/modify those. This is likely to work if the difference between the two Appian versions is not huge. (It is likely to work easily from 7.8 to 7.7)<br /><br />By removing/modifying I mean, either find some way to keep that functionality but use functions which are compatible with older version also. For this you may need to do some modifications in your application. This will however not work if your application has some features which can be implemented only in new version of Appian. So, in that case your only option is to remove that functionality from the application to be able to import to old Appian env. For example: WebAPI cannot be imported to old versions. So, for application import to succeed on old version, you will need to remove the WebAPIs from your application when exporting.<br /><br />For the a!queryProcessAnalytics() function, you will need to replace it with the code which uses Portal to SAIL Plugin. Then you can use it on old version also.(Of course you will have overhead of deploying the plugin for that from forum). Also, you will effectively need to maintain redundant code - one code which uses portal to SAIL plugin(for old Appian version), other which uses a!queryProcessAnalytics() for newer version. This is certainly an extra overhead, but it will help in porting applications to slightly older versions.<div style="clear:both;"></div>https://community.appian.com/thread/31570?ContentTypeID=1Thu, 26 May 2016 11:14:02 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b54f3fab-4c71-4657-b83c-8008ef097145sikhivahansOut of curiosity, I would like to ask a question here. Does this mean that we need to remove the features of the later version so that it matches the prior version? For instance, let&#39;s say an application was developed on 7.8 making use of a!queryProcessAnalytics(). In order to import it into 7.7, do we need to remove the references of a!queryProcessAnalytics apart from updating the Manifest file?<div style="clear:both;"></div>https://community.appian.com/thread/31568?ContentTypeID=1Thu, 26 May 2016 11:05:28 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b128bd34-81f2-4913-ab45-33b20789ac1bchetany1. Offcially, Appian does not support importing applications developed on a newer version to an older version environment.<br />2. But, it is possible to do so. You can edit the Manifest.MF file in the package and edit the version. This will basically bypass the check that Appian makes for version check.<br />Then, as next step you can remove features which are supported in new version of Appian but not in old version. <br />3. For this case, you can remove the TestCases from the expression rules.<br />If it still gives an error, then the solution by Rachel of editing the xml and removing the testConfig also works.<br /> This is not officially supported but it can be useful when you do want to import on older version.<div style="clear:both;"></div>https://community.appian.com/thread/31552?ContentTypeID=1Wed, 25 May 2016 20:46:31 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:5aedf50b-d900-4adf-ad59-d11d6fd5cff0rachelz585Hi again all,<br /><br />Just wanted you to know that I was able to successfully import all objects by modifying their xml files from &lt;name&gt;RuleTestConfig?List&lt;/name&gt; to &lt;name&gt;RuleTestConfig&lt;/name&gt;<br /><br />Thanks<div style="clear:both;"></div>https://community.appian.com/thread/31548?ContentTypeID=1Wed, 25 May 2016 19:48:31 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:e1c2f585-cc0d-451d-aed2-7584b58702b9Sachin PandeyBackward compatibility is not supported in Appian.<div style="clear:both;"></div>https://community.appian.com/thread/31545?ContentTypeID=1Wed, 25 May 2016 18:57:33 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:ed1ddb53-ce94-417e-bc66-444eef0c7e9bPaul MayeurBackward import is not supported by Appian<div style="clear:both;"></div>https://community.appian.com/thread/31544?ContentTypeID=1Wed, 25 May 2016 18:49:00 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:181919ab-8361-4492-8e57-b321b96c1fcesikhivahansTo add some more information, &#39;Cautions&#39; section in the Application Deployment Guidelines Topic in the documentation reads as follows: &quot;Application packages from an earlier version can be imported by later versions. Packages exported from later versions of Appian are not compatible for importing into prior versions.&quot;<div style="clear:both;"></div>https://community.appian.com/thread/31543?ContentTypeID=1Wed, 25 May 2016 18:45:54 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:c07cb7dd-a2a4-4fc9-982e-281eee380023rachelz585Yes, I did notice that was the case on one rule, but no test cases are saved for the rest.<div style="clear:both;"></div>https://community.appian.com/thread/31542?ContentTypeID=1Wed, 25 May 2016 18:43:42 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:620a6e5a-6cd6-4c96-be8d-f1b92919eb49Lakshmi MeyyappanThat being said, it&#39;s not recommended to import to an older environment. It can be done by modifying the export, as you have found, however it&#39;s better to upgrade the second environment so that you can import the application as-is.<div style="clear:both;"></div>https://community.appian.com/thread/31541?ContentTypeID=1Wed, 25 May 2016 18:42:06 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:0db97b0e-b43a-4940-aee4-41e828d2c63dLakshmi MeyyappanIn 7.11, Test Cases were added to Expression Rules (see the 7.11 Release Notes <a href="https://forum.appian.com/suite/help/7.11/Appian_Release_Notes.html#Appian_Designer)">forum.appian.com/.../Appian_Release_Notes.html</a>. It looks like you have a rule that has a test case saved, but 7.10 doesn&#39;t support it. I would try removing the test case and then exporting again.<div style="clear:both;"></div>https://community.appian.com/thread/31540?ContentTypeID=1Wed, 25 May 2016 18:41:33 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:6bb92aac-8d8c-40fd-a089-944f4b0ef475sikhivahans@rachelz Hi, to the best of my knowledge, what you have been trying to do isn't possible. You can only import the application into an environment that makes use of 7.11 or above. Also as far as my knowledge is considered, manifest file just provides us with the information re the version of Appian in which the build took place and changing it won't have any significance.<div style="clear:both;"></div>