Unknown alerts often arise from incomplete data or missing portfolio attributes. You may also encounter errors that are caused by undefined issues.

We strongly recommend that all our clients promptly address these uncertainties. Neglecting them could lead to missed disclosures, uncomfortable conversations with regulatory bodies, and overall dissatisfaction.

If you receive an Unknown result and are unsure how to resolve it, first navigate to the Missing Data page. This can be accessed directly in your environment by navigating to Monitoring > Shareholding Disclosure > Results > Missing Data. This screen is also accessible via the main Results List screen at the top.

Each Unknown alert will be grouped by issue, including which assets and rules are affected.

Depending on the specific issue, it may be possible to address the missing data by applying data overrides. Ultimately, you would want to ensure your upload files are updated directly, but data overrides allow you to fix these problems immediately.

Should you need any additional assistance, please get in touch with our Support team via the In-App Messenger or by email at support@fundapps.co.

Unknowns can occur when data is missing for rules with preconditions. These missing data issues can arise for a variety of reasons, including:

Reason: 1 error occurred: The GetRuleValue function found Unknown results within the group 'XYZ' for the rule 'MajorCA-IR-Pre'.

To resolve such Unknowns, you may have to navigate to the previous NavDate for that issuer to identify and resolve what is missing. For example, on July 2nd, I saw an Undefined error for the Canada Insider Report rule for Nokia. To resolve this, navigate to July 1st (or the first day you started trading Nokia), and the missing property will appear. Once you resolve that missing data point, the undefined issue should go away.

Some properties are not referenced in our Technical Documentation or are Portfolio attributes, such as OriginalPortfolioInvestmentManager13F. Here's a quick guide on how to fix them:

Some properties are calculated from inputs provided in the positions file; we refer to these as calculated properties. If you don't provide the required properties for the calculation, the system will generate Unknowns or Missing Data alerts.

Properties such as CountryOfIncorporation and CountryOfIssue are vitally important in order for FundApps to determine which country a position may be disclosable in. For example, if CountryOfIncorporation is not provided, FundApps will flag Unknowns in all rules that this security could potentially fall under. This is likely to cause a large number of unknowns due to the large number of rules relying on this property.

The number of Unknown alerts might initially appear daunting; however, we suggest consulting your environment's Missing Data page. This will provide a concise overview of the absent properties and the corresponding impacted rules.

If you are absolutely unable to source the CountryOfIncorporation for a security, we recommend setting the CountryOfIncorporation to “??,” which means the position will be evaluated against each rule in FundApps and will not cause Unknown results. Positions set with CountryOfIncorporation="??" will be tracked under a Control Rule, and a separate article on these rules is available here.

A missing IssuerId will almost certainly result in multiple Unknowns for the same rule, since most disclosure results are grouped by this property. In fact, assets with a missing (or blank) IssuerId will likely generate a large number of Unknowns. FundApps is configured this way purposefully. Since rules are often grouped by IssuerId, results will not be delivered for:

Consider an example where there's a holding in Vodafone Equity (5%) and a holding in Travis Perkins Equity (10%). If we remove the IssuerId from the Travis Perkins Equity, an unknown would be triggered with the message, "Assets checked by this rule have missing data: IssuerId."

These Unknowns are triggered because the system has no way of knowing whether the 10% result should be grouped with the 5% Vodafone result. To put it another way, there are two possibilities for the Vodafone result:

It is, therefore, vitally important that IssuerId is always provided and in a consistent manner. If you absolutely cannot find a value for the IssuerId, set it to “UNKNOWN” so that all unknown IssuerIds are grouped together.