#Apsona0 discussing

Most of our donations are sent through the mail. The are scanned and deposited by the bank, and they send us the scans. We look at the scans and enter each gift (batch item) individually. We have been using Apsona for batch entry. It's a completely manual process and terribly time consuming. 

I have been exploring ways to automate the process. BofA first said they could send the data directly into SF, but then backpedaled. Apparently, since it's not an accounting software, they can't connect to it. The bank can send us a spreadsheet with all the data, so we can upload it into a batch. Apsona said that we could upload the batch items and review and commit manually. Then they said we couldn't. 

This morning I got a message from Apsona saying that batch items could not be imported in bulk. I am so disappointed. 

I am searching for another solution. As our org grows, manual batch entry will become untenable. Do you have a better way to handle mailed donations?  

We are currently using NPSP, but are planning to migrate to NPC in FY27, so a future solution is also worth consdiering.... thanks for your help! 

#Apsona #Batch Gift Entries

Hi, everyone! I am testing an email & document merge in #Apsona. My Word file is in the Documents object in Salesforce. When the PDF is generated after the merge, any apostrophes are being formatted funky. :(  

Any tips on how to format apostrophes properly in the Word document so there is no issue showing them as they should be once the PDF is generated? Thank you! @Apsona for Salesforce @Nonprofit Success Pack @Nonprofit Ask Me Anything (Global) @Salesforce.org System Administrators @Salesforce.org MVPs @Thanooj Pamanji

Hi, everyone! I am testing an email & document merge in #Apsona. After creating an Org-Wide Email Address, I tested as a user to see if they could select it for the Sender field in the merge/mail action. Even though it is associated with their profile, they are unable to select it when specifying a Sender ("Default - current user's name and email" is the only option.) :( 

I ensured that the "Organization-wide From Email Address" is included in the Visible Objects for their Apsona Configuration for their profile, but after I save the configuration, the object still does not show in the visible objects list. Any ideas on why this may not be working as expected? Thank you! 

@Apsona for Salesforce @Nonprofit Success Pack @Salesforce.org MVPs @Salesforce.org System Administrators @Nonprofit Ask Me Anything (Global) @Thanooj Pamanji

#Nonprofit

Hi, everyone! I am trying to add a standard Opportunity field as a column in an #Apsona report but cannot select it when searching for the field. I confirmed the following: 

• The Apsona configuration for the profile gives access to ALL Opportunity fields 
• FLS for the field is Read for the profile 

I also cleared the cache and still cannot see the field -- any tips as to why? Thank you! @Apsona for Salesforce #NPSP #Nonprofit Success Pack #Nonprofit

My org has been advised to upgrade Apsona by Apsona's Tech Support to clear out some potential issues that users have been experiencing with filters. They shared this documentation

to follow as we perform the upgrade. Before doing such an upgrade, we'd like to test in the sandbox how it may impact our system, customizations, integrations, etc.  

• What are some potential issues to be cognizant of? 
• Will there be any impact to users, reports, merge actions, etc. once upgraded? 
• Any tips on items that should be thoroughly tested/reviewed before making the upgrade in Production? 

Additionally, when it comes to Apsona updates, patches, etc., how often would you recommend we upgrade the app for our org? 

Any and all help would be much appreciated. Thank you! 

If anyone has an Apsona account and 2 minutes, I'd like to ask anyone to upvote my Apsona idea to be able to document merge a single document with different footers. It is super helpful to be able to print a word doc with different footers  based on donation, membership, and DAF payments for our CEO to sign Thank you letters!   

We have a filter in our multi-step report that is looking for specific Account records. This record was recently created about a month ago. When we try to find that account in one of the filters, we get the following error message: 

Name , Id From Account where Name like '%florida%' order by Id

^

ERROR at Row:1:Column:38

The operator like is not supported on an encrypted field

sfdcService: get Account get-Account-121

soql was:

Select Name , Id From Account where Name like '%florida%' order by Id asc limit 201"

Other Accounts that were created long ago don't have any issues being pulled into the report. But for whatever reason, this newish Account can't get searched for in the filter without being hit with the error message. We've cleared caches for the entire org, and unfortunately, that didn't resolve the issue for myself (a sys admin) and our users.   

Any help into the error message would be much appreciated! 

Hello! Our team is new to Apsona and excited to bring together disparate objects for donor discovery and visit planning. We are curious if anyone has used Apsona to be a 'radius search' of sorts? A use-case example would be:  

• Generate a list of contacts within 25 miles of New York City
  • Be able to report on those results across objects.

Right now we're utilizing Salesforce Maps and placing the individuals into a campaign then filtering on reports based on that campaign. That'd be easy enough to do in Apsona as well but are curious if anyone has had luck filtering within a distance on zip-code, county, etc.

We're exploring an Apsona trial right now and I was wondering if it is possible to nest sublists.

Particularly, we would like to merge documents on for multiple accounts that list their opportunities and each opportunity has a sub object to relate it to multiple campaigns, so we'd like to list the campaigns as a comma-separated list in one table row for each opportunity.

I found the documentation for a comma separated list (https://www.apsona.com/pages/sfdc/doc/doc-merge-combine-list-fields.html), but it doesn't mention whether it would work inside a table and when I tried it out I didn't see the list group option, just the table group option. So, I wanted to check if it is even possible to do that or if I just set it up wrong.

#Apsona #Apsona Document Merge

@Apsona for Salesforce,

I am still struggling with a question that I brought to the Apsona Office Hours last Thursday.

I need to build an cross filter report in Apsona that only includes records where the child object does not match the criteria (an exception report).

I was able to create the report I am looking for natively in Salesforce but I cannot figure out how to create the report in Apsona.

Here is a screenshot from the Salesforce report. #Apsona #Apsona Document Merge