ValueX Exception

[Former Member]

Hi SDNers,

I facing a problem.

When I am importing a record into MDM the file went to Exception folder (ValueX Folder).

When I see Log for that file it is showing an error like this:

*<Failure ts="2009/04/08 13:54:25.275 GMT" tid="2488" entry-no="85013" operation="Import" import-action="Create" row="3">

One or more uniqueness constraints were violated by this operation</Failure>*

Any quick solution. ASAP

Thanks

Ravi

[Former Member]

Hi Ravi,

Kindly update the thread status.

Regards,

Jitesh Talreja

[Former Member]

Hi,

If you want the fields to be sortable in Data Manager or in the portal then set Sort Index = Normal. You will find two arrows along with field name with the help of which you can sort the field values either in ascending order or in descending order.

But it is not recommended to make all the fileds sortable since it affects the loading time of repository.

Regards,

Jitesh Talreja

[Former Member]

Hi Ravi,

Check thre 3rd row in your source file.

It should have a field or a record in which a field is having a duplicate value.

Open the console and check that particular field in the repository.

The unique property for that field might be set to yes.

Either change the unique property to no or change the source file to ensure that the value doesnt get repeated.

Hope it helps.

Thanks,

Minaz

[Former Member]

Hi Manaz,

What is teh use of Sort Index in Console. (Normal or None) in field detail.

Thanks

Ravi

[Former Member]

Hi Ravi,

Open the MDM Console and Connect to the repository. Select the repository and on the right hand side you will see the Unique fields of your repository. That means the fields visible in Unique Fields should have different values in all the records. If you try to import the records having field values already exists for some other records then it violates the Unique constraint. Either remove the Unique fileds by unloading the repository and remove the fields from Unique fields or import the records having different values for the fields which are unique.

Regards,

Jitesh Talreja

[Former Member]

Hi Ravi,

A ValueX or an ImportX exception points that there is a problem with your Records and not structure of Import.

The error message clearly mentions that the error is with the Unique contraint being violated.

It means thers a particlar record or records in your sorce file which should be having a Unique value for a particular field that you have set in console Do not have a unique value .

As a result it is failing the import.You can open the file in the exception folder to specific view which record or records have violated the contraints and then perform the necessary action of either changing its value manully or changing the field property in Console.

So say for eg you have made a field Mat number as Unique in Console but while importing you are having 2 records with the same material number.So it means it violating the Unique property as a result the record is moving to the exception folder.

So you can either manully edit the XML file and change the Material num to a unique value or cahnge the Unique property in console so that it allows deplicate values under that field.

Hope It Helped

Thanks & Regards

Simona Pinto

[Former Member]

Hi Ravi,

When I am importing a record into MDM the file went to Exception folder (ValueX Folder).

When I see Log for that file it is showing an error like this:

*<Failure ts="2009/04/08 13:54:25.275 GMT" tid="2488" entry-no="85013" operation="Import" import-action="Create" row="3">

One or more uniqueness constraints were violated by this operation</Failure>*

Looking at the error, the problem should be in Row 3 of your file. The value for the field in Row 3 should be most probably violating the Uniqueness constrainst that you must have put in Console in the Field Setting.

Another easier way is to go to the Console and in the Main table, check for all the fields which have been defined as Unique. ( Sort on the Unique Tab to make it simplere).

You can then compare the fields and their values in XML file that you are trying to import. Any 1 data might be already present in your MDM data Manager. So kindly change the incoming data or else change the setting of Unique for that particular field as per your business requirement.

Hope it helps.

Thanks and Regards

Nitin Jain

[Former Member]

Hi Nitin,

Thanks for your Response

You mean Unique Means Unique filed right in Console.

with the Row "3" Value only I am importing Data. If it is already present in MDM the with that number then the record should be updated in MDM right.

Can you please be little bit clear?

Thanks

Ravi

[Former Member]

HI Ravi,

You mean Unique Means Unique filed right in Console.

with the Row "3" Value only I am importing Data. If it is already present in MDM the with that number then the record should be updated in MDM right.

Right Ravi. One of The field property is Unique. You must have set the Unique property of any field as " YES". That means for that field if a value 123 is present in MDM, and if you are trying to import a file which has the same value 123 for that field, it will throw an error.

So if you are trying to update any record which is already present, open the import map and choose the Unique field as the Matching field.

ad then choose the default import action as " Update Mapped fields" for existing record.

It will solve your problem

Thanks and Regards

Nitin Jain

[Former Member]

Hi Ravi,

It shows that the record you are trying to import is violating the uniqueness constraint for the field(s). Either you need to make the changes in the data so that the uniqueness constraint should not get violated or remove the uniqueness constraint from the MDM Console by reseting the Unique property of the fields.

Regards,

Jitesh Talreja