Handle Non-Unique Values This page last changed on Feb 26, 2008. .stickable, h1, h2, h3, h4, h5 false true Show Sticky notes Hide Sticky notes Save Cancel Oracle Data Service Integrator Documentation > Data Services Developer's Guide # How To Handle Non-Unique Values This topic describes how to handle an update map that is disabled because two values in a return type map to one value in a data source. Example See Also ## Example In a query map, you might attempt to map one value in a data source to two values in an XML return type. When the update map is generated and the flow is reversed, two values map from the return type to one in the data source, which creates an update error. ##### An Error from a Non-Unique Value The cause of the error is that two values are attempting to update one in the data source. This creates a build error in the logical data service, and you cannot deploy or test it. You cannot right-click and enable the update block either. The update doesn't work unless you write a custom update function in XQSE. The best solution is to disable the multiple mapping in the Query Map tab: Click Query Map. Delete the mapping line from the data source to the second, duplicate element in the return type. This should reverse the error. Save the data service and click Update Map to check the change. If the error still exists, right-click and choose Revert Customizations. ## See Also ##### Concepts Understanding Update Maps Recognize When Something is Wrong ##### How Tos Change a Mapping Remove a Mapping Revert Customizations

Document generated by Confluence on Jan 13, 2009 15:57