https://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entitiesen-USTelligent Community 12https://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entitiesMon, 23 Jul 2018 17:39:32 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:225a2a1b-35ed-4c53-a347-1fbc5da44c81Jordan Horwathttps://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities#commentsCurrent Revision posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 5:39:32 PM<br /> <div class="row content_container"> <table style="background-color:#bcedaf;"> <tbody> <tr> <td>This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.</td> </tr> </tbody> </table> <h2 id="symptoms">Symptoms</h2> <p>When importing an updated data store with new entities, any object referencing the new entity in the package fails to import. The import log throws an error saying that the object failed to import due to a missing entity in the data store:</p> <pre><code>Problems (1): content xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx &quot;&lt;name&gt;&quot;: The content [id= uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] was not imported because a required reference is missing: Reference to entity [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] in data store [id=1074 uuid=_a-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_1101] cannot be found. (APNX-1-4070-004) (APNX-1-4071-006) </code></pre> <h2 id="cause">Cause</h2> <p>This issue has been resolved via <strong>AN-50362</strong> in Appian 16.3.</p> <h2 id="action">Action</h2> <p>Upgrade to the latest version of Appian to take advantage of the fix.</p> <h2 id="workaround">Workaround</h2> <p>To work around this issue, perform one of the following:</p> <ol> <li>Try importing the package twice.</li> <li>Split up the package into two imports. First, import a patch that contains only the updated data store and any relevant CDTs. Publish the new version of the data store and verify mappings. Then, import the other objects in a separate package.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to Appian 16.2 and earlier.</p> </div> <p>Last Reviewed: July 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, application design, fixed issues, import/export</div> https://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities/revision/5Thu, 13 Jul 2017 15:57:53 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:225a2a1b-35ed-4c53-a347-1fbc5da44c81Nick Vigilantehttps://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities#commentsRevision 5 posted to Appian Knowledge Base by Nick Vigilante on 7/13/2017 3:57:53 PM<br /> <div class="row content_container"> <table style="background-color:#bcedaf;"> <tbody> <tr> <td>This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.</td> </tr> </tbody> </table> <h2 id="symptoms">Symptoms</h2> <p>When importing an updated data store with new entities, any object referencing the new entity in the package fails to import. The import log throws an error saying that the object failed to import due to a missing entity in the data store:</p> <pre><code>Problems (1): content xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx &quot;&lt;name&gt;&quot;: The content [id= uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] was not imported because a required reference is missing: Reference to entity [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] in data store [id=1074 uuid=_a-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_1101] cannot be found. (APNX-1-4070-004) (APNX-1-4071-006) </code></pre> <h2 id="cause">Cause</h2> <p>This issue has been resolved via <strong>AN-50362</strong> in Appian 16.3.</p> <h2 id="action">Action</h2> <p>Upgrade to the latest version of Appian to take advantage of the fix.</p> <h2 id="workaround">Workaround</h2> <p>To work around this issue, perform one of the following:</p> <ol> <li>Try importing the package twice.</li> <li>Split up the package into two imports. First, import a patch that contains only the updated data store and any relevant CDTs. Publish the new version of the data store and verify mappings. Then, import the other objects in a separate package.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to Appian 16.2 and earlier.</p> </div> <p>Last Reviewed: July 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, fixed issues, import/export</div> https://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities/revision/1Tue, 07 Mar 2017 16:52:57 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:225a2a1b-35ed-4c53-a347-1fbc5da44c81Nick Vigilantehttps://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities#commentsRevision 1 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 4:52:57 PM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>When importing an updated data store with new entities, any object referencing the new entity in the package fails to import. The import log throws an error saying that the object failed to import due to a missing entity in the data store:</p> <pre><code>Problems (1): content xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx &quot;&lt;name&gt;&quot;: The content [id= uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] was not imported because a required reference is missing: Reference to entity [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] in data store [id=1074 uuid=_a-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_1101] cannot be found. (APNX-1-4070-004) (APNX-1-4071-006) </code></pre> <h2 id="cause">Cause</h2> <p>This issue has been resolved via <strong>AN-50362</strong> in Appian 16.3.</p> <h2 id="action">Action</h2> <p>Upgrade to the latest version of Appian to take advantage of the fix.</p> <h2 id="workaround">Workaround</h2> <p>To work around this issue, perform one of the following:</p> <ol> <li>Try importing the package twice</li> <li>Split up the package into two imports. First, import a patch that contains only the updated data store and any relevant CDTs. Publish the new version of the data store and verify mappings. Then, import the other objects in a separate package.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to Appian 16.2 and earlier.</p> </div> <p>Last Reviewed: January 2017</p> <div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, fixed issues, import/export</div> https://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities/revision/4Tue, 07 Mar 2017 11:56:35 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:225a2a1b-35ed-4c53-a347-1fbc5da44c81Nick Vigilantehttps://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities#commentsRevision 4 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 11:56:35 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>When importing an updated data store with new entities, any object referencing the new entity in the package fails to import. The import log throws an error saying that the object failed to import due to a missing entity in the data store:</p> <pre><code>Problems (1): content xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx &quot;&lt;name&gt;&quot;: The content [id= uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] was not imported because a required reference is missing: Reference to entity [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] in data store [id=1074 uuid=_a-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_1101] cannot be found. (APNX-1-4070-004) (APNX-1-4071-006) </code></pre> <h2 id="cause">Cause</h2> <p>This issue has been resolved via <strong>AN-50362</strong> in Appian 16.3.</p> <h2 id="action">Action</h2> <p>Upgrade to the latest version of Appian to take advantage of the fix.</p> <h2 id="workaround">Workaround</h2> <p>To work around this issue, perform one of the following:</p> <ol> <li>Try importing the package twice</li> <li>Split up the package into two imports. First, import a patch that contains only the updated data store and any relevant CDTs. Publish the new version of the data store and verify mappings. Then, import the other objects in a separate package.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to Appian 16.2 and earlier.</p> </div> <p>Last Reviewed: March 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, fixed issues, import/export</div> https://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities/revision/3Tue, 07 Mar 2017 11:54:15 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:225a2a1b-35ed-4c53-a347-1fbc5da44c81Nick Vigilantehttps://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities#commentsRevision 3 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 11:54:15 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>When importing an updated data store with new entities, any object referencing the new entity in the package fails to import. The import log throws an error saying that the object failed to import due to a missing entity in the data store:</p> <pre><code>Problems (1): content xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx &quot;&lt;name&gt;&quot;: The content [id= uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] was not imported because a required reference is missing: Reference to entity [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] in data store [id=1074 uuid=_a-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_1101] cannot be found. (APNX-1-4070-004) (APNX-1-4071-006) </code></pre> <h2 id="cause">Cause</h2> <p>This issue has been resolved via <strong>AN-50362</strong> in Appian 16.3.</p> <h2 id="action">Action</h2> <p>Upgrade to the latest version of Appian to take advantage of the fix.</p> <h2 id="workaround">Workaround</h2> <p>To work around this issue, perform one of the following:</p> <ol> <li>Try importing the package twice</li> <li>Split up the package into two imports. First, import a patch that contains only the updated data store and any relevant CDTs. Publish the new version of the data store and verify mappings. Then, import the other objects in a separate package.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to Appian 16.2 and earlier.</p> </div> <p>Last Reviewed: January 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, fixed issues, import/export</div> https://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities/revision/2Tue, 07 Mar 2017 11:54:06 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:225a2a1b-35ed-4c53-a347-1fbc5da44c81Nick Vigilantehttps://community.appian.com/support/w/kb/508/kb-1302-the-content-id-was-not-imported-because-a-required-reference-is-missing-reference-to-entity-entity-in-data-store-data-store-cannot-be-found-error-thrown-when-importing-an-updated-data-store-with-new-entities#commentsRevision 2 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 11:54:06 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>When importing an updated data store with new entities, any object referencing the new entity in the package fails to import. The import log throws an error saying that the object failed to import due to a missing entity in the data store:</p> <pre><code>Problems (1): content xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx &quot;&lt;name&gt;&quot;: The content [id= uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] was not imported because a required reference is missing: Reference to entity [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] in data store [id=1074 uuid=_a-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_1101] cannot be found. (APNX-1-4070-004) (APNX-1-4071-006) </code></pre> <h2 id="cause">Cause</h2> <p>This issue has been resolved via <strong>AN-50362</strong> in Appian 16.3.</p> <h2 id="action">Action</h2> <p>Upgrade to the latest version of Appian to take advantage of the fix.</p> <h2 id="workaround">Workaround</h2> <p>To work around this issue, perform one of the following:</p> <ol> <li>Try importing the package twice</li> <li>Split up the package into two imports. First, import a patch that contains only the updated data store and any relevant CDTs. Publish the new version of the data store and verify mappings. Then, import the other objects in a separate package.</li> </ol> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to Appian 16.2 and earlier.</p> </div> <p>Last Reviewed: January 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, fixed issues, import/export</div>