IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Add in_reference_table check to Information Analyzer or allow variable to be bound to n-tuples instead of single fields

In Information Analyzer one can implement a reference check against only a single column using in_reference_column. But in many cases you need to check references against a set of columns. E.g. imagine  you need to implement a simple address check using city and postal code. If you have a reference table that contains all valid combinations of postal codes and cities (postCode, city). Currently you cannot implement this directly with a in_reference_column check as you can either check against the postCode or the city, but not the combination of it. Imagine you had a in_reference_table check where you code specify multiple columns like this:

(sourceCity, sourcePostCode) in_reference_table (refPostCode, refCity)


Currently without this function you need to create a view over the reference table that merges the 2 columns into a single column and you need to concatenate the source columns. This is significant effort to implement and it looks ugly.

Generally it would be nice if a variable in a data rule can be bound to an n-tuple instead of a single column / field. This would allow a much greater flexibility and reuse. E.g. imagine you a data rule definition:

A Exists


Currently this can only be bound to a single field like e.g. CreditCardNo. But it cannot be bound to CreditCardNo and CreditCardExpirationDate at the same time. To verify credit card information exists you would need to write instead:

A Exists and B Exists

If you could bind (CreditCardNo, CreditCardExpirationDate) to a single variable you dont need this, but you can stick to a simple A Exists data rule definition, increasing the re-use of data rule definitions significantly. The bound rule would look like this then:

(CreditCardNo, CreditCardExpirationDate) Exists

With it you also do not need an additional in_reference_table check, but you could stick to the in_reference_column check.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Mar 6 2019
  • Future consideration
Idea Priority High
Customer Name NordLB
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions