If you haven’t, you should read our Boomi’s cross-reference table lookup component blog. It talks all about support using a regular expression as a matching rule and how flexible it is to have this feature.

Note: The matching rule supports regular expression as well.



Although it may be much simpler than using the regular expression, it is still a very useful and powerful feature to consider. This especially including designing an integration process that requires a xRef Table in the mix. Below is our example use case for future references:


Often leads may come from different channels off a marketing application, however, they should only be parked under a single parent lead source in a CRM application instead. For example:

  • Channel in Marketing App value of: WEB-1, WEB-2, WEB-3, WEB-N (where N being running number) would indicate a website source.
  • Channel in Marketing App value of: CAMP-1, CAMP-2, CAMP-3, CAMP-N (where N being running number) would indicate a campaign source instead.


It would take serval rows if the “Exact Match” rule is being used. It would be difficult to predict how many rows are needed for the specific channel. In this particular case, consider that the running number could be ever growing.


While this is achievable with a regular expression, those not familiar with regular expression should consider utilising a wildcard to achieve the correct mapping result too! It could be as clean and easy to maintain as the screenshot below: