Order-to-cash dashboard missing invoice data after Data Lake refresh

ERP Infor CloudSuite
, , , , , , , ,
1

After refreshing our Infor Data Lake last weekend, our order-to-cash dashboard is showing incomplete invoice data. Specifically, invoices created in the past 30 days are completely missing from the revenue tracking reports, while older invoices (60+ days) appear correctly.

I checked the Data Lake ingestion job logs and they show successful completion with no errors. However, when I query the invoice table directly, I can see the recent invoices are there but they’re not appearing in the reporting workspace. The invoice table mapping looks correct in the data model, but I’m wondering if there’s a filter or date range issue that got reset during the refresh.

Here’s what I’m seeing when I check the invoice count:

SELEXT COUNT(*) FROM DL_INVOICE
WHERE INVOICE_DATE >= '2025-04-22'
-- Returns 0 rows in dashboard, but 847 rows in direct query

This is impacting our revenue tracking and month-end close process. Has anyone experienced similar issues after a Data Lake refresh?

system 2

Here’s the complete solution addressing all three focus areas:

1. Data Lake Ingestion Job Configuration The root cause is that your Data Lake refresh created a new partition scheme, but the ingestion job didn’t backfill recent data into the new structure. You need to run a targeted delta load:

-- Trigger delta ingestion for missing date range
EXEC DL_INVOICE_DELTA_LOAD
  @StartDate = '2025-04-22',
  @EndDate = GETDATE()

This forces the ingestion job to re-process the last 30 days of invoice data and load it into the new partition structure. Check the job logs afterward to confirm all 847 invoices were processed.

2. Invoice Table Mapping Verification After the delta load completes, refresh your reporting workspace metadata to recognize the new partition scheme:

  • Navigate to Data Source Configuration in your reporting tool
  • Click “Refresh Schema” to detect the new monthly partitions
  • Verify that the invoice table mapping includes these key fields: INVOICE_ID, INVOICE_DATE, INVOICE_STATUS, ORDER_ID, CUSTOMER_ID
  • Check that the join relationships to ORDER and CUSTOMER tables are still intact

If any mappings are broken, recreate them using the Data Lake schema browser. The refresh may have changed some column names or data types, particularly for date fields.

3. Reporting Workspace Filter Update This is critical to prevent recurrence. Your dashboard filters need to be dynamic, not static:

Replace any hardcoded date filters like:

WHERE INVOICE_DATE >= '2025-04-22'

With relative date functions:

WHERE INVOICE_DATE >= DATEADD(day, -30, CURRENT_DATE)
  AND INVOICE_STATUS IN ('POSTED', 'PAID')

Also check workspace-level default filters:

  • Remove any absolute date range filters (e.g., “2024-01-01 to 2025-03-31”)
  • Set default filters to “Last 90 Days” or “Current Month” using relative date parameters
  • Ensure invoice status filters include all relevant codes (POSTED, PAID, PENDING) unless you specifically want to exclude certain statuses

Post-Fix Validation:

  1. Run the delta ingestion job and confirm 847 invoices loaded
  2. Refresh workspace schema and verify new partitions appear
  3. Update dashboard queries to use relative dates
  4. Test the order-to-cash dashboard - all recent invoices should now appear
  5. Schedule regular delta loads (daily or weekly) to keep data current between major refreshes

The combination of backfilling missing data, updating schema mappings, and converting to dynamic filters will resolve your immediate issue and prevent it from happening after future Data Lake refreshes.

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.

3

Check your reporting workspace filter settings. After a Data Lake refresh, sometimes the default date filters get reset to historical ranges. Look at the workspace-level filters in your order-to-cash dashboard configuration and make sure the invoice date range isn’t hardcoded to exclude recent data.

5

I’ve seen this happen when the Data Lake refresh changes the partition scheme for invoice tables. If your reporting workspace is still pointing to the old partition key or date range, it won’t pick up the newly loaded data. Check if the refresh created new partitions and whether your dashboard queries are parameterized to use dynamic date ranges instead of static ones. Also verify that the invoice table mapping includes all the necessary join keys to link invoices with orders and customers.

6

Good catch on the partition scheme. I checked and the Data Lake refresh did create new monthly partitions. The dashboard configuration still references the old partition structure. How do I update the workspace to recognize the new partitions without breaking existing reports?

8

You need to refresh the metadata in your reporting workspace. Go to the data source configuration and run a schema refresh to pick up the new partition structure. Then update any hardcoded date filters in your dashboard queries to use relative date functions like CURRENT_DATE - 30 instead of static dates. This will prevent the issue from recurring after future refreshes.

9

Also check if the Data Lake ingestion job is correctly mapping the invoice status field. Sometimes after a refresh, the status codes change or get remapped, and invoices in certain statuses get filtered out. Verify that your dashboard isn’t excluding invoices based on a status filter that no longer matches the new data structure.

10

One more thing - check the Data Lake replication lag settings. After a major refresh, sometimes the replication job needs to catch up on recent transactions. You might need to manually trigger a delta load to pull in the missing 30 days of invoice data.