Apsona for Salesforce

Hi @Natalie Gorman, “batch” turns out to mean quite different things from tool to tool, so these are the questions I’d put to each one on your list:

• How does a batch start? From a list view or report, on a schedule, or only through a Flow you build yourself? The Flow route works, but your client then has something extra to maintain.
• What does “attachment” mean in each tool? Some save the document as a File on the record (the Files related list), others as an old-style Attachment (Notes & Attachments). Files are easier to preview, share and find in Lightning, so it’s worth checking which one you get. Also check who can see it afterwards.
• How does printing work? Can the batch give you one merged PDF to print in one go, or do you end up with 200 separate files to open?
• What does the limit count? Documents, users or runs. With regular batches, a per-document cap is usually where the cost grows.

Full disclosure: I work on Floverk, a document-generation tool, so I’m not neutral. Your case is exactly what it’s built for: one document per record, each saved as a File on its record, plus one merged PDF for printing. We’re currently looking for a few companies to use it early, free for a period, in exchange for feedback. If your client might be up for that, I’m happy to share details. Either way, the questions above should help whichever tool you pick.

Hi Anna, 

Per Apsona's own documentation, mixing "matches" and "does not match" linkages to different previous steps within the same "all" grouping is officially supported — their docs give this exact pattern as a valid example ("select those contacts that match the Contact ID values of step 3, but do not match the Contact ID values of step 1"). So the structure itself isn't wrong on its face. 

Since you're getting essentially the full dataset back, the most likely explanations are: 

1. The "Exclude given Cash gift" step itself isn't returning what you expect. A "does not match" linkage only excludes records that actually show up in that step's own result set. If that step's filter criteria (on the Opportunity object) is too narrow, returns 0 rows, or isn't filtering the way you think, the negation has nothing to exclude against — meaning it will pass everything through, which would exactly explain seeing your full 18k. Run "Exclude given Cash gift" as a standalone step first and confirm its row count/content looks right on its own before trusting the negation against it. 

2. Null values on Opportunity.Primary Contact. If a meaningful number of Opportunity records in that step have a blank Primary Contact, those nulls typically don't behave intuitively in a match/does-not-match join — they often don't count as a "match" either way, which can cause a "does not match" filter to effectively let everything through rather than excluding records that have no related Opportunity at all. Worth checking how many rows in that step actually have Primary Contact populated. 

3. Isolate one linkage at a time. Temporarily delete the "Active DD" and "Grab from TEMP campaign" linkages and run with only the "Exclude given Cash gift — does not match" linkage active. If the count still doesn't drop at all, that confirms the negation itself isn't being applied as expected, rather than an interaction between the three conditions. 

Since this is specific to how Apsona's engine resolves negated linkages (not a native Salesforce reporting behavior I can verify beyond their docs), if isolating the linkage above shows it's genuinely not filtering even on its own, that's worth taking directly to Apsona support via the "Help for this section" link on that page — this is exactly the kind of linkage-resolution edge case their support team would need to look at on the backend, since the doc confirms the feature should work but doesn't cover every interaction case.

Hi Wendy!

GAU Allocations should generally be tied to the Opportunity/Opportunity Contact or payment record, but whether they appear in an Apsona Batch Export depends on the fields and relationships included in the export. 

Since the Campaign and GAU Allocations are already on the Opportunity, I’d first check the Batch Export configuration and make sure the GAU Allocation object/related fields are included. If the export is only pulling Opportunity fields, the GAU Allocation records won’t automatically appear. 

I’d also verify whether the allocations are created before the Batch Export runs and that the Opportunity is the record actually being matched to the payment.

If you can share the Apsona Batch Export configuration (especially the source object and selected fields/relationships), it would be easier to pinpoint exactly where the allocations are being dropped.

Hi @David Cheng

Thank you for flagging this. We have updated the links in the website now to point to the correct links. 

Thanks, 

Abhishek 

Team Apsona

Hi @Benjamin engh

, 

If you're trying to use the Scheduler in a sandbox org, you'll need to have it enabled for that sandbox first. Please reach out to our Licensing team at sales@apsona.com

, and they will enable the Scheduler for your sandbox. Once it's been enabled, simply clear your Apsona cache, and the Scheduler options should become available. 

If you have any questions or need further assistance, please feel free to reach out. We are always happy to help. 

Thanks, 

Abhishek 

Team Apsona