Avoiding Cyclic Parameter Error Using Lookup Datasets in Wyn

Background: 

When designing reports in Wyn, parameters are often used to filter data dynamically. A common approach is to populate parameter values using a dataset query (“From Query”).
However, the following error may be encountered when previewing reports:

“Cyclic report parameter references detected”

This typically happens when parameters and datasets are configured in a way that creates circular dependencies.

This article explains why this happens and how to properly use lookup datasets to avoid such issues.

Common Scenario

A report may have parameters, and the same dataset used to generate the report is also used to:

  • Populate parameter available values
  • Filter data based on those same parameters

This creates a circular logic:

  • Dataset depends on parameter
  • Parameter depends on datasetResult: Cyclic dependency error

Root Cause

The issue arises when the same dataset is used both to populate parameter values and to retrieve filtered report data. In this configuration, the dataset depends on parameter values to return results, while the parameter depends on the dataset to determine its available values.

This creates a circular dependency where neither the dataset nor the parameter can be resolved first. As a result, Wyn throws a cyclic reference error and prevents the report from rendering.

Recommended Solution

The recommended solution for this type of error is to use ‘Lookup datasets’. Using separate lookup datasets is not only a fix for cyclic errors but also a recommended design practice. Lookup datasets are typically smaller and more efficient, as they return only the values needed for parameter selection. This reduces processing load and improves report performance.

Reusing the main dataset for parameter population can introduce unnecessary complexity and performance overhead. More importantly, it increases the risk of circular dependencies, especially when parameters are cascaded or interdependent.

Therefore, the report should include two different types of datasets:

  1. Main Report Dataset
    • Used to retrieve and display report data
    • Consumes parameter values
  2. Lookup Dataset(s)
    • Used only to populate parameter available values
    • Should NOT depend on report parameters

Steps to follow: 

  1. Add a new dataset based on your Model Entity

2. Edit the parameter

3. Make sure the report is populated from the correct dataset

Enea Gega

Enea Gega

Enea is a Technical Product Enablement Specialist for the Wyn Enterprise Platform. He acts as a vital bridge between customers, product teams, and engineering to ensure that every new feature delivers genuine value and drives user adoption.

Enea specializes in translating complex customer needs into actionable insights for product roadmaps and technical documentation. By partnering cross-functionally, he ensures seamless delivery readiness and alignment across all releases.