Difference between revisions of "Notes on Unpacking"
From SmartWiki
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
When you unpack '''UTA Data Exchange''' packages there are three possibilities: | When you unpack '''UTA Data Exchange''' packages there are three possibilities: | ||
* The data is successfully unpacked. | * The data is successfully unpacked. | ||
| − | * The data cannot be unpacked due to '''Import Rule''' violation. Import rules are used to ensure that new data types for | + | * The data cannot be unpacked due to '''Import Rule''' violation. Import rules are used to ensure that new data types for {{l1}}, {{l2}} and {{l3}} cannot be imported. |
* The package cannot be unpacked due to a decryption key error or an '''Internal System Error'''. | * The package cannot be unpacked due to a decryption key error or an '''Internal System Error'''. | ||
The following table outlines the possible unpack messages: | The following table outlines the possible unpack messages: | ||
| − | + | {| border="1" | |
| + | |'''Message''' | ||
| + | |'''Notes''' | ||
| + | |- | ||
| + | |Unpack Successful! | ||
| + | |No action required. | ||
| + | |- | ||
| + | |Unpack Failed: Package violates Import Rules. | ||
| + | |Click the ''View Details'' link. | ||
| + | |- | ||
| + | |Level One Template Type - Template Name in package doesn't exist in current system.<br>Contact package provider to resolve this issue. | ||
| + | |View Details - Import Rules Violation.<br>Note: ''Template name'' will be replaced by actual template name. | ||
| + | |- | ||
| + | |Level One Template Type - Level 2 Type Name in package doesn't exist in current system.<br>Contact package provider to resolve this issue. | ||
| + | |View Details - Import Rules Violation.<br>Note: ''Level 2 Type Name'' will be replaced by actual Level 2 Type name. | ||
| + | |- | ||
| + | |Level One Template Type - Level 3 Type Name in package doesn't exist in current system.<br>Contact package provider to resolve this issue. | ||
| + | |View Details - Import Rules Violation.<br>Note: ''Level 3 Type Name'' will be replaced by actual Level 3 Type name. | ||
| + | |- | ||
| + | |Unpack Failed: Possible Cause - Invalid Decryption Key or Invalid Package.<br>Check the Error Log for details on the Incoming Packages page. | ||
| + | |Unpack confirmation page. | ||
| + | |- | ||
| + | |Unpack Failed: Internal Error. | ||
| + | |View details. | ||
| + | |- | ||
| + | |Unable to Unzip File: Possible Cause - Invalid Decryption Key | ||
| + | |View details. | ||
| + | |- | ||
| + | |Unpack Failed: Invalid Decryption Key Version | ||
| + | |View details. | ||
| + | |} | ||
| − | [[ | + | ==See Also== |
| + | * [[SmartSimple Support Desk]] | ||
| + | |||
| + | [[Category:Data Exchange]] | ||
Latest revision as of 12:14, 14 August 2013
When you unpack UTA Data Exchange packages there are three possibilities:
- The data is successfully unpacked.
- The data cannot be unpacked due to Import Rule violation. Import rules are used to ensure that new data types for Level 1, Level 2 and Level 3 cannot be imported.
- The package cannot be unpacked due to a decryption key error or an Internal System Error.
The following table outlines the possible unpack messages:
| Message | Notes |
| Unpack Successful! | No action required. |
| Unpack Failed: Package violates Import Rules. | Click the View Details link. |
| Level One Template Type - Template Name in package doesn't exist in current system. Contact package provider to resolve this issue. |
View Details - Import Rules Violation. Note: Template name will be replaced by actual template name. |
| Level One Template Type - Level 2 Type Name in package doesn't exist in current system. Contact package provider to resolve this issue. |
View Details - Import Rules Violation. Note: Level 2 Type Name will be replaced by actual Level 2 Type name. |
| Level One Template Type - Level 3 Type Name in package doesn't exist in current system. Contact package provider to resolve this issue. |
View Details - Import Rules Violation. Note: Level 3 Type Name will be replaced by actual Level 3 Type name. |
| Unpack Failed: Possible Cause - Invalid Decryption Key or Invalid Package. Check the Error Log for details on the Incoming Packages page. |
Unpack confirmation page. |
| Unpack Failed: Internal Error. | View details. |
| Unable to Unzip File: Possible Cause - Invalid Decryption Key | View details. |
| Unpack Failed: Invalid Decryption Key Version | View details. |
