RSA Identity Governance and Lifecycle error "The selected file does not match the required CSV format" when importing Local Entitlement Definitions
4 years ago
Originally Published: 2017-03-03
Article Number
000064852
Applies To
RSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 6.9.1, 7.0.0, 7.0.1
 
Issue

RSA Identity Governance and Lifecycle generates the following error message when importing Local Entitlement Definitions:
 
The selected file does not match the required CSV format
 
This happens when the following steps are followed:
  1. From the Applications menu, select an application and then select the Import button.
User-added image
 
  1. For CSV file to import, select the Browse button to import your CSV file:
User-added image
  1. The following warning message is displayed and entitlements are not imported. 
User-added image
 
  1. The following errors are logged in the aveksaServer.log file (in 7.0.x located in /home/oracle/wildfly-8.2.0.Final/standalone/log/aveksaServer.log or in 6.9.1 located in /home/oracle/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/log/aveksaServer.log )
03/03/2017 17:38:31.864 ERROR (default task-6) [com.aveksa.server.core.ManualEntitlementImporter] 
com.aveksa.server.core.ManualEntitlementImporter$AbortProcessing: Resource entry is not found or is null
  
03/03/2017 17:38:31.865 ERROR (default task-6) [com.aveksa.gui.pages.admin.rawEntitlement.edit.ImportApplicationEntitlementsDialogData] 
com.aveksa.server.core.AdminServiceException: Bad data encountered:MyLocalEntitlementA : 
MyActon,MyLocalEntitlementCollector,MyActon,"Long Description Line1 ::Resource entry is not found or is null

 
Cause
This issue may occur if the imported data contains embedded line feed and carriage return characters that are not handled by the CSV export format.  This may cause the column data to miss-align. 

This may occur for example if the database import is created from a database export of the Entitlements view from another instance of RSA Identity Governance and Lifecycle and that export contains the multi-line field Long Description.
 
User-added image
Resolution
This is an inherent limitation of the CSV file import format and will not be addressed in the product. 
Workaround
The following techniques may be used to work around this limitation. 
  1. Avoid using multiple lines in the Long Description field.
  2. If the database import is created from a database export of the Entitlements view from another instance of RSA Identity Governance and Lifecycle ensure you do not export the Long Description field. 
User-added image
  1. Edit the CSV file in Excel or a text editor before importing and remove the Long Description column, or edit the contents so the description does not contain line feeds. 
User-added image

Related Articles

Trending Articles

Don't see what you're looking for?