Guided Matching FAQs

What are the known limitations?

Guided Matching does not support roll-up summary fields of transactions on the related transaction set.

What triggers Guided Matching?

Guided Matching is triggered by status changes on Transaction an Inbound Report records to New or Unmatched.

When is a Guided Matching job automatically retried?

When the job fails and the exception message contains UNABLE_TO_LOCK_ROW, the job is retried.

Where is the Guided Matching setup stored?

The setup is stored in the custom object Guided Matching Setup (cpm__Guided_Matching_Setup__c) as a JSON file. These records can be used to quickly implement the same setup in another org by copying the JSON to the new record.

If an inbound report fails, does FinDock automatically retry Guided Matching?

Failed status indicates there is an issue with the inbound report that needs to be resolved. Once the issue is resolved, you can manually retry Guided Matching on the record, either all rules or just the rule that failed.

How should I use Guided Review?

This one needs a longer response, so see the separate Guided Review FAQ for details.

Why do I get an error about a "cycle in rule dependencies"?

If FinDock cannot calculate the matching logic in a rule execution plan, you will see the following error which blocks you from saving your Guided Matching setup:

The system has been unable to calculate a full rule execution plan. This is almost certainly because of a cycle in rule dependencies. Save is disabled until this issue has been resolved.

The first thing you should check if you see this error are the entry criteria for your rules. By default, every rule has an "if empty" criterion. If you add more entry criteria, but have an equals/not equals value empty, you will get the above error. You have two entry criteria that are the same because both equal "if empty" in practice, so their logical relationship cannot be determined.