BIA Business Process Copy
After doing a full install of Issues Management and then BIA, with plenty of minor errors, the BIA Business Process Copy data feed will not import correctly. The Loss Events do not auto-map, and neither do the Evaluated Business Processes. The Key Field Definitions shows Business Unit(1), which seems to be an error. For Loss Events in Key Field Definitions, the field name shows an empty drop-down.
I've moved this thread to the https://community.rsa.com/community/products/archer-grc/archer-customer-partner-community?sr=search&searchId=40d19932-5591-420d-bd14-1f0b6607f0b7&searchIndex=0 so that you can get an answer to your question.
Those errors would seem to be related to the install of the applications, and not the import of the data feed. Are you sure you've cleaned up all the install messages?
I have not been able to clean up all of the error messages. A base install of Issues Management won't even complete without a large amount of Minor Failure messages. Most are field errors due to 'inability to find the related module.' Two reports provide a Log Reference ID, but I don't know how to look it up and find more information. My understanding from the documentation was that the errors could be ignored.
All of those minor failures are related to things you must not have licensed, or if you've licensed a lot of things, then your key is not setup correctly. Try cleaning up the installation issues before importing the feed.
Things like "Business Unit(1)" generally indicate an improper mapping whereby a duplicate field was created. Empty drop downs for key fields usually mean you don't have a license for the application you are trying to specify a key for.
I have a feeling the differences between standard and federal installations is causing me issues. Our current production environment has no Business Unit and several applications are named differently (Findings/POA&Ms). How disparate are standard and Federal installs? Should I be following a different install procedure?
There are overlapping application ids between federal and core Archer applications. For example, Business Unit and Office have the same application id, but have different names and different layouts. This means that if you package install Business Unit when you already have Office installed, then Business Unit will try to overwrite your Office application. The easiest way to package install core into a federal instance or federal into a core instance, is to select "Create New Only" and "Do not override layouts" during package install, then you can drag any new fields/objects onto the layout after install. Below I have added a table that shows where federal and core overlap.
Risk Acceptance (RBD)
Missions / Processes