After upgrading to the latest ICS 2021 release, our lease analytics dashboard is missing several custom fields that we use for IFRS 16 compliance reporting. The standard lease fields display correctly, but all custom fields we added for tracking lease modifications and extension options have disappeared from the dashboard.
I checked the underlying data tables and the custom field data is still there, but the dashboard schema doesn’t seem to recognize them anymore. This is creating compliance risk because we can’t generate the required lease modification reports for our auditors. The custom field migration process during the upgrade might not have updated the dashboard properly.
Has anyone experienced custom fields disappearing from Infor Analytics dashboards after an upgrade? I need to understand if this is a dashboard schema update issue or if the field mappings need to be reconfigured manually.
I’ve helped several clients resolve this issue post-upgrade. Here’s the comprehensive solution covering all three focus areas:
Custom Field Migration:
The upgrade doesn’t automatically migrate custom field definitions to the analytics layer. You need to manually re-register them:
First, verify custom fields exist in CloudSuite data dictionary:
Navigate to CloudSuite Admin > Data Dictionary > Lease Management
Document the custom field names, data types, and source tables
Common custom fields: lease_modification_date, extension_option_terms, renewal_probability
Register custom fields in Infor Analytics data dictionary:
Go to Infor Analytics Admin > Data Dictionary > Lease Management
Click Add Custom Field for each missing field
Match the field name, data type, and source table exactly as defined in CloudSuite
Set the field category to ‘Custom’ and mark as ‘Reportable’
Dashboard Schema Update:
After registering custom fields, update the dashboard schema:
Check that data from the source tables is flowing correctly
Validate date fields are formatted properly for IFRS 16 calculations
Update ETL configuration to include custom fields:
Navigate to Analytics Admin > ETL Jobs > Lease Data Extract
Edit the field selection to include all custom fields
Schedule an immediate ETL run to populate historical data
Set up incremental refresh to keep custom fields synchronized
Recreate compliance report templates:
The upgrade may have reset report templates to default configurations
Open Report Designer and add custom fields back to your IFRS 16 compliance reports
Test the lease modification report with sample data
Validate calculations using custom fields (extension options, modification dates)
The root cause is that CloudSuite upgrades treat custom fields as tenant-specific customizations that aren’t automatically migrated to the analytics layer. The analytics platform requires explicit field registration and ETL configuration updates.
After completing these steps, run a full ETL refresh to populate historical custom field data in the analytics database. Your compliance reports should then show all custom fields with complete data. If specific fields still don’t appear, check the source table permissions - the analytics ETL account needs read access to custom field columns.
Document your custom field mappings in a configuration guide for future upgrades. This will streamline the migration process and prevent compliance reporting gaps during the next release update.
This draft is based on general Infor CloudSuite knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
This is a known issue with ICS 2021 upgrades. The dashboard schema doesn’t automatically pick up custom fields after a release update. You need to manually refresh the data model in Infor Analytics. Go to Admin Console > Data Models > Lease Management and click Refresh Schema. This should make the custom fields visible again in the dashboard designer.
I tried refreshing the schema but the custom fields still don’t appear in the dashboard. When I check the data model definition, I can see the base lease tables but not the custom field extensions. Is there a separate step to migrate custom field definitions during an upgrade?
The upgrade process doesn’t automatically migrate custom field metadata to the analytics layer. You need to re-register the custom fields in the analytics data dictionary. Go to Infor Analytics Admin > Data Dictionary > Lease Management module and add each custom field with its data type and source table mapping. Once registered, refresh the dashboard and the fields should appear in your reports.
Tested this on CloudSuite 2023.x — re-registering custom fields like lease_modification_date through Admin > Data Dictionary immediately restored them in the analytics dashboard layer.
We had the same problem after our upgrade. The issue is that custom fields defined in CloudSuite don’t automatically sync to the analytics data model. You have to create explicit field mappings in the analytics configuration. Check if your custom fields are defined in the CloudSuite data dictionary first, then create corresponding entries in the Analytics data dictionary with matching field names and types.
Also verify that the custom fields are included in the ETL process that feeds the analytics dashboard. Sometimes upgrades reset the ETL field selection, and custom fields get excluded from the data extraction. Check your ETL job configuration and make sure the custom field columns are selected for extraction from the source lease tables.