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 result in overlooked 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 if there is missing data for rules that have preconditions.

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 the 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 it will show the missing property. Once you resolve that missing data point, the undefined issue should go away.

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

There are some properties that are calculated based on the input properties, and we refer to these as calculated properties. If you don't provide the required property for calculation, the system will generate an Unknown or Missing Data alert.

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 volume of unknowns might initially appear daunting at times; however, we suggest consulting your environment's Missing Data tab. This section will provide a concise overview of the absent properties and the corresponding impacted rules, as illustrated below.

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 rule results. Positions set with CountryOfIncorporation="??" will be included under Warning instead. These are known as Control Rules, and a separate article on these can be found here. The result of setting the property to "??" is shown below.

A missing IssuerId will almost certainly create multiple Unknowns for the same rule, as most disclosure results are grouped by this property. In fact, assets with a missing (or blank) IssuerId will likely create a very large number of unknowns, as FundApps will evaluate it against many rules. FundApps is configured this way purposefully. Since rules are often grouped by IssuerId, results will not be delivered for:

Consider the example: we hold a Vodafone Equity (5%) and a Travis Perkins Equity (10%). If we remove the IssuerId from the Travis Perkins Equity, then an unknown would trigger 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 MajorGB 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 all unknown IssuerIds will be grouped together.