Flow error when creating new allocations

[nhardenVenn]

Error Occurred:

An Apex error occurred: System.NullPointerException: Attempt to de-reference a null object

How should I handle this error? I'm only seeing it when allocations are created. In this case we are summing up fund allocation amounts to the fund.

Side question: Does apex-rollup play nice with NPSP?

Thank you,

Nate

[nhardenVenn]

[jamessimone]

@nhardenVenn any chance you can keep your Apex Developer Console open while debugging the flow and report the full stacktrace for that error? I'll look into this on my end but at the moment, with the information provided, it's not clear where/how the error is occurring.

[jamessimone]

On the subject of NPSP - I have several non-profits using Apex Rollup in conjunction with NPSP, yes.

[nhardenVenn]

apex-07L8Z00005Zu833UAB.log
I think this is what you're asking for...

[nhardenVenn]

or this.

[jamessimone]

Thanks - either of the above was fine.

Since you have this flow rollup set to start from the parent records, you need to fill out the optional Calc Item Type When Rollup Started From Parent field on your rollup action.

[jamessimone]

I will be fixing this in the upcoming release, however, so that you don't have to provide that argument since it lives on the Rollup CMDT - that was just a miss on my part as far as putting this functionality together for the bulk invocable action. Apologies!

[nhardenVenn]

<img width="1194" alt="Screen Shot 2022-06-23 at 2 03 38 PM" src="https://user-images.githubusercontent.com/107888703/175378011-1f45bddb-034b-4d22-9331-15d9fda

c090e.png">

Here is what I have at the moment. It doesn't like a filed I have in the where clause on my CMDT. What am I missing?

Thank you,

Nate

[nhardenVenn]

I left this out from above.

[jamessimone]

@nhardenVenn awesome, thanks for the screenshots - those really help! Is Intacct_Sync_Status__c a field on Fund Allocation?

[nhardenVenn]

yes.

[jamessimone]

Great. I'll have this issue wrapped up in just a bit. I don't know if you have seen my comments in #336 but there is current a block with packaging that will prevent me from releasing these changes - the current guidance is that packaging will be possible again late today, or tomorrow. I'll keep you apprised.

[jamessimone]

@nhardenVenn the new version just released should fix this for you!

[nhardenVenn]

This is great, thank you very much!

I do have a question, though.

I currently have it calculating from the parent object with the Recalculate Rollup Button, but is it possible to also allow the rollup calculation to trigger from the child simultaneously? Or do I have to choose one or the other?

Thank you,

Nate

[jamessimone]

@nhardenVenn yes, that is possible. as long as you don't actually have a flow/apex trigger calling Apex Rollup from the parent, and are only using the parent recalc button to qualify the CMDT records set up like that, then you can also have the children trigger the rollup with separate records!