Re: Line Item Subset Summary Level, workaround needed please!
@rob_marshall - Hmm... no I am not using collect, and don't want to use collect for this setup.
In the video LiSS Creation is a constants module, with only Line Items. This is the module I point the LiSS to when creating it.
Module B is a Data Load module (List 1 x LISS Numbers x Versions x Time x Line Item (amount)
This is where I am loading data, not in the LiSS Creation module.
A collect statement would pull the numbers from LiSS Creation not Module B.
In the Summary Report, I want to pull the final number from Module B.
You may be wondering why create a LiSS in a Constants Module, the value add, is both the Data Load module and other override modules only have 1 line item instead of 4. In this oversimplified example 1 vs. 4 is not that big of a difference. But in my real world example I have 100, 200, or 300 numbers being added together.
So in essence I am reducing hundreds of line items down to 1 which is both easier to audit and maintain.
I'm surprised my formula didn't work. I specifically reproduced in my workspace and reviewed your video 🙂 Did the LI MAP work correctly? Is its format the same LI on which the SUM formula is written?
In my example it didn’t work only then, the spell you have in the last module also has the same reference as in the example (in our example, LISS with number 4). I reviewed the video and there is no such thing.
We have two general problem for LOOKUP:
1. LOOKUP doesn’t work with summary “Formula” (SELECT works).
2. LOOKUP is not designed to work with the aggregate items on non-composite lists (lists with no parent hierarchy defined). (Copy from Anapedia).
You can try SELECT, but since you can have hundreds of LIs, in theory you may need to choose a different non-list element instead of number 4. this story will not be flexible (PLANS).