Identity does not have a mapping

Cause: This means that PI MDB has access permissions for a PI identity (or PI user or PI group) that does not have a PI mapping. Every PI identity, user, or group that has PI MDB access permissions must have at least one PI mapping. If you delete the last mapping, you create a security conflict between PI MDB and PI AF.

Consequences: You cannot edit PI MDB access permissions for the affected modules, except to delete the identity that does not have mapping. You can still edit the module itself.

Fix: Create a new mapping for the relevant identity, user, or group. Alternatively, delete the PI MDB access permissions for that identity, user, or group.

Note: AF Link does not automatically pick up changes in mappings. The change does not take effect until you edit the element in some way; this triggers AF Link to update the settings in MDB.