MDM 7.1 SP9 Duplicate Record functionality

[former_member208981]

Hi SDNers,

This is in MDM 7.1 SP 9 version.

In Data Manager:

1.       Selected a record to duplicate.

2.       Before the new duplicate record gets saved, click the mouse 4 times, it creates 4 duplicate records. All exactly with same values.

Ideally MDM does not allow this. Only 1 record gets duplicated.

Please check and revert.

Thanks,

Priti

[Former Member · Accepted solution]

Hi Priti,

Yes you are correct,this happens in MDM 7.1 SP 09.

I have not tried in other versions but the steps to reproduce this are -

1.Click on duplicate

2.As the other record starts saving and click numerous times.

Its takes a few attempts to do this though

I think this happens because of the time lag that it takes to process the records.

Good observation,please go ahead raising a OSS and share your findings.

Thanks,

Ravi

[Former Member · Accepted solution]

Hi Ravi,

It does not happen in SP07 as i had tried to replicate this.

So i think this bug is introduced in SP09 itself. Thank you.

[Former Member · Accepted solution]

Hi Ankush,

Appreciate that.I would say its not a major bug but a fix is certainly needed for this,waiting for Priti's update.

Thanks for sharing.

Thanks,

Ravi

[former_member208981 · Accepted solution]

Thanks all for the replies.

Thanks Ravi for checking and confirming this at your end.

We have raised an OSS note for it. Will keep you posted on any updates.

Thanks,

Priti

[Former Member]

Hi Priti,

We are pretty sure that MDM does not allow something of this sort. Other then trying activities of replicating in different repositories and environements, i would also suggest to check the hardware component connected to your machine(just incase). If this prolongs in other environements even after performing few basic steps like Unloading/loading repository, please raise OSS note as suggesed.

Regards,

Ali

[Former Member]

Hi Priti,

If you are facing this issue then i would suggest you to try to replicate this issue in different repositories and different environments.

In case this issue is same, then you should raise OSS to SAP to fix this bug.

Please update me on your findings as well.

Thanks and Regards,

Ankush