Value Exceptions - Import Map Update

[Former Member]

Hello MDM Gurus,

We have the requirement to update the existing import map by unmapping two of the fields that we no longer required.

When we try unmapping the required fields and save as another map name, export, reimporting it and overwriting the existing map with the same name. But the problem is we are loosing all value mappings. we are facing issue getting loads of value exceptions as all value mappings are gone.

Please we need experts advices to resolve this since we no longer need that two fields getting imported in to the repository.

We need a solution to unmap that two fields and keep all existing value mappings.

Save Update not works for filed mappings, it only works for value mappings.

Thank you very much in advance for the suggestions and inputs.

Example :

Field1 and Field2 Unmapped, We saved the Map by Save -> we are loosing all value exceptions ( As it stores only present config)

Field1 and Field2 Unmapped, We saved the Map by Save Update -> When reimport the map again, we are seeing this field1 and field2 still mapped.

Field1 and Field2 Unmapped, We saved the map by Save As -> Still it does like First Scenario.

Please Advice.

[former_member226173]

Hi,

Field1 and Field2 Unmapped, We saved the Map by Save Update -> When reimport the map again, we are seeing this field1 and field2 still mapped.

I had faced a similar issue and the problem was because i didnt have proper authorisation to save the maps .

Please check if you have the credencials to save and update the maps .

Regards,

Vignesh

[Former Member]

Hi Smartsoft,

Just try this below procedure and revert with result.

1. Open the existing map.

2. Remove all the fields from matching field under Match Records tab.

3. Now unmap these two not required fields under Map Field/Value tab.

4. Afterwards, set again all the matching fields like earlier under Match records tab. Now make sure that under your Import Status tab Action Item: Ready to Import. Once it is done.

5. Now try with Save As option as a new map in order you have had existing correct map as a reference for future.

If it work properly then you can overwrite this new map name with existing map. Kindly revert.

Regards,

Mandeep Saini

[Former Member]

Thanks Mandeep for your Answer,

Unmapped fields and value mappings present in the correct xml file is stored/updated correctly in the map. But when i try executing with different xml file with different values, facing value exceptions , endup saying that value needs to be mapped.

I think we need to delete that map and load the updated map to the port. i have to try this and see.

[Former Member]

Hi Smartsoft,

What is/are the type of these fields?

If you have tried the above mentioned ways and still it does not work can we redefine the problem and hide these fields from portal and also replace the current value with null in Data Manager,also in conversion filter set NULL value or dummy value.

If not try one more thing,create a super xml containing all the possible combinations of these field values and do a save update.

Retest if it works.

Thanks,

Ravi

[Former Member]

Hi,

Just a trial and error suggestions -

Once you save your new map, try to export it and save a copy.

Now in the repository delete the existing old map.

Import the new saved map and check.

Thanks,

Shambhu.