0
Declined

Attributes with the same name - Read-Only problem in MIM

Paul Zelenewicz 3 years ago in UNIFYBroker/Aurion updated by Matthew Davis (Engineering Manager) 1 year ago 4

UNIFYBroker v5.3.1

Aurion API Connector v5.3.0

MIM 2016SP1 - 4.4.1749.0

Problem:

I have an 'Aurion Person' adapter and an 'Aurion ESS' adapter - each with an attribute called PersonNumber.

In 'Aurion Person' the attribute is read-only, in 'Aurion ESS' the attribute is not read-only.

Broker settings - Single Schema mode is false.

When I create the Aurion ESS Management Agent in MIM and attempt to setup an export attribute flow to  PersonNumber, MIM reports that the attribute is read-only.

It makes no difference if I create the ESS management agent before the Person management agent (even in a vanilla MIM database).

If I apply a rename transform to the PersonNumber in the ESS adapter I am able to setup an export attribute flow to the renamed attribute (i.e., ESSPersonNumber).

Question: 

Is it a specific requirement for Broker to maintain unique attribute names throughout different adapters? 

Affected Versions:
Fixed by Version:

Answer

Answer
Declined

Closing as LDAP was providing the correct information to MIM, and no other information was provided. Feel free to re-open if the issue persists or resurfaces.

Under review

There is no requirement for name uniqueness across adapters unless using single schema mode.

Are you able to trace the schema request when setting up the MA?

Does an attribute rename transformation on one of the attributes fix up the issue?

Does an attribute rename transformation on one of the attributes fix up the issue?

Didn't see you had already answered this. Is this suitable workaround for now and we address this when we can?

Yeah that's not a problem. I've already applied the rename to avoid the issue during migration.

Answer
Declined

Closing as LDAP was providing the correct information to MIM, and no other information was provided. Feel free to re-open if the issue persists or resurfaces.