Hi,
I’ve hit a frustrating architectural wall with SuiteAnalytics Workbooks involving Dataset Linking and the ARM (Revenue Recognition) module, and I'm hoping to get some expert insights or a potential workaround.
The Setup & Workflow:
- Dataset 1 (Base): Built on the
Revenue Recognition Plan record type. From this dataset, I successfully pull data across the ARM chain: Revenue Arrangement -> Revenue Element -> Revenue Plan. From the Revenue Element record, I am pulling the Created From field, which gives me the source Sales Order Number.- (Quick side question here: Is it truly blocked by the Analytics schema to pull additional Transaction Header fields directly upwards via the
Created From / Source join in a single Revenue Plan dataset, without being limited just to the document number?)
- Dataset 2 (Joined): Since I couldn't pull more Sales Order fields in Dataset 1, I created a second dataset running on the
Transaction record type to fetch all the necessary Header-level fields from the Sales Order and its associated Project. - The Workbook: I linked these two datasets in a Workbook using the Sales Order Number as the common key (Text to Text link) and started designing the Pivot Table Layout.
The Problem (See Screenshots):The dataset link works perfectly in theory, but the Pivot Table engine breaks down completely depending on where I place the Amount field in the Layout:
- Scenario A (Screenshot 1 - Ideal Layout but missing data): When I place the
Amount field in the Measures section, the rows group perfectly by SO Number and the months pivot beautifully. HOWEVER, every single Header-level field brought from Dataset 2 evaluates to null and displays as "- No Project Name -", "- No Sales Rep -", etc. - Scenario B (Screenshot 2 - Header Data appears but Layout breaks): If I move the
Amount field to the Columns section (leaving Measures empty), the row splits into two. Suddenly, the top row correctly displays the Sales Order Header fields from Dataset 2, while the bottom row holds the revenue plan data.
My Question:It seems the Workbook engine cannot aggregate or display dimensions from a linked dataset when a Measure is actively calculating across multiple rows from the base dataset.
Has anyone encountered this specific Dataset Linking behavior with ARM data? Is there a UI/Layout workaround to force the Measure to coexist with the linked Header fields on the same row, or is SuiteQL the absolute only way to achieve this matrix?
Any advice from the NetSuite gurus here is highly appreciated!