Skip to main content

#Ariaid-title30 utenti parlano di questo argomento

Anne Emerson ha fatto una domanda in Nonprofit Success Pack

I tried to do a mail merge of a Word doc from the Activity History of a custom object. Received a series of error messages related to npsp. I am the system admin and have an active user account so not sure what this means.

 

Error Type: Batch Apex error

Error Date: 2023-06-05 05:00:20

[INACTIVE_OWNER_OR_USER] owner or user is inactive. [and then my org ID]

Context: npsp__RD2_OpportunityEvaluation_BATCH

 

Here were the other errors:

 

Context: npsp__CRLP_Account_BATCH

Context: npsp__ADDR_Seasonal_SCHED

Context: npsp__CRLP_Account_AccSoftCredit_BATCH

Context: npsp__CRLP_Account_BATCH

Context: npsp__CRLP_Account_SoftCredit_BATCH

Context: npsp__CRLP_Account_SoftCredit_BATCH

Context: npsp__CRLP_Contact_BATCH

Context: npsp__CRLP_Contact_BATCH

Context: npsp__CRLP_RD_BATCH

Context: npsp__CRLP_SkewDispatcher_BATCH

etc.

3 risposte
  1. 6 giu 2023, 05:29

    Hi @Anne Emerson ,

     

    When you deactivate a user that is the running user of a batch job, then these errors begin to appear. You can change the running user for those jobs to yourself to fix this, just follow the steps outlined here - https://powerofus.force.com/s/article/NPSP-Edit-or-Reschedule-NPSP-Scheduled-Jobs #Ariaid-title3

     

    https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000BttxpSAB

There is a button on the Account page Related Tab called "New Account Donation." Not all of our entries are donations and now I have a new person coming in to do ad sales. In the future we may have others who are selling sponsorships or vendor booths.

Can I edit this standard button to New Opportunity?

Google Fu sends me to Global Actions, but I don't see it there and I've hit a dead end. thanks!

@Fundraising@Nonprofit Get Started Hub@Nonprofit Success Pack@Salesforce.org System Administrators
8 risposte

I am setting up a student database. I have imported a list of students who all belong to one department. Different groups of students are enrolled in several programs at the department. How can I simultaneously affiliate them to one account (department) and enroll into one program? (Not to do it manually, one by one for each student contact).

@Nonprofit Get Started Hub@Education Data Architecture
3 risposte
  1. 13 mar 2019, 14:29
    No problem @Olga Skriabikova

    ! Unfortunately I am unable to see the images you shared. Can you upload them again?

    Here are some thoughts based on your questions:

    Question 1: When importing from the CSV file, I arranged the “department” column to be matched with the “Department” field of the Contact. However, on an individual contact page, the department (nor Primary department, for that matter) is shown.

    Thought: The issue here may reside in the configuration of HEDA after it was installed. I want you to review the steps outlined here (

    https://powerofus.force.com/articles/Resource/HEDA-Install-and-Configure#!#ariaid-title3

    ) and let me know what you find. I'm thinking the issue has to do with the Page Layout.

    Question 2: I also do not see, for example, the phone number. I am not sure why. I can see both of these fields in the overview of all accounts. Please see print screens below. Do you have an idea why this happens? What am I doing wrong?

    Thought: I'm thinking the issue here is the same as Question 1 above. Also - consider how TDTM is used to populates a Contact's standard Email and Phone fields based on Preferred Email and Preferred Phone selections.

    Question 3: Is it possible to somehow remove the fields which are not relevant for my organization (for example, FEPRA tick-box and Citizenship box)? In the documentation it reads that fields are customizable, but when I try to remove it, I receive an error message stating “The component you are attempting to delete is part of a managed package, and cannot be deleted.”

    Thought: The error you received says it all 🙂

    Question 4: What can I do to at least not see it? (The administration staff will not appreciate seeing all different fields that are not relevant or useful for us in any way).

    Thought: You can certainly hide fields on a page layout. But before doing this you may want to consider cloning the specific HEDA page layout first. I say this because if you are using a single page layout for every profile and remove a field on that page layout then no one will be able to see it (other than the Admin). If you clone a page layout be sure to assign the layout to the profile(s) using it.

Hi, I've followed the directions to create a 'New (Record Type - in this case 'Donation')' action in Lightning to complete our migration from Classic and it's not working. Any suggestions as to what I'm doing wrong? I had it working in the sandbox and I can't spot the difference. I couldn't get it to migrate in a change set so I just tried to recreate it and no dice. I feel like I'm going insane. Here's the instructions I'm referencing: https://powerofus.force.com/articles/Resource/NPSP-Add-Edit-Opp-Button-Contacts Thanks!

7 risposte
  1. 28 feb 2019, 17:04
    Couple o' questions: 1) when you say you couldn't get it to migrate, what errors were you getting that was preventing it, 2) are you getting an error when you push the button you recreated or is just nothing happening, and 3) if you are trying to create a specific record type, does your profile have the ability to create that record type?

How do you assign a new Lightning Home Page to be the default home page for classic apps that cannot be upgraded to Lightning? We have a few Lightning Home Pages that were created by another person no longer here in the Activation Assignments that have "All Classic Apps*" for the app name and then a profile assigned to it. You cannot assign classic apps on that screen. Where do you do it?

@Education Data Architecture@* Lightning Now! *
14 risposte
  1. 5 mar 2019, 22:45
    I was going to suggest re-creating your own HEDA app but then wondered if Jace had tricks I didn't know about. Re-creating will definitely allow you more flexibility to do what you want to do.

The company is on NPSP version 3.146. The Level Object exists on the org. The Salesforce video on creating levels says go to App Launcher and type Levels in the search. On this org, that search comes up empty. What needs to be set up to make Levels available? Thanks.

@Nonprofit Success Pack@Salesforce.org System Administrators
3 risposte
Hi Artur, welcome to the Hub! Please take a moment to upload your photo and complete your profile. You might be interested in joining our Higher Ed group here: https://powerofus.force.com/_ui/core/chatter/groups/GroupProfilePage?g=0F980000000CjRY. If you need some help navigating the Hub, check out the 'Getting Started' resources below. Finally, if you have any questions or concerns, please let me know how can I help. Welcome aboard!

Getting Started in the Hub

7 commenti

@Nonprofit Success Pack @Judi Sohn (salesforce.com)

 

The article in question: https://powerofus.force.com/articles/Resource/Known-NPSP-Issues-in-Lightning-Experience#!#ariaid-title3

 

Regarding the first fix: "Creating Opportunities from Contact Records"... 

I just want to know WHERE Users actually view/access (Launch) the 'New-Action' that's been successfully created?

3 risposte
  1. 15 ago 2018, 19:24
    @R Philip Callahan The most common reason why folks can't see the Action is if their profile doesn't have visibility to the Primary Contact field on the Opportunity. Go to Setup > Object Manager > Opportunity. Click on the Primary Contact field, then 'Set Field Level Security.' Make sure it's visible to your profile and not Read-Only.
K. Trlb ha fatto una domanda in Education Data Architecture

I understand the tradeoff that Table-Driven Trigger Management (TDTM) makes between modularity and efficiency.

 

As my Programming 102 professor said, "If you want to solve a problem more easily, add a layer of abstraction.  If you want to make a program run faster, remove a layer of abstraction."

 

In studying up on HEDA, I'm reading about TDTM at https://powerofus.force.com/articles/Resource/HEDA-Manage-Trigger-Handlers and feel a little stab in my chest when I see separate helper classes for each business process (an entire helper class just to manage "Do Not Contact" preferences?!).

 

  • Yes, it's very readable.  But ouch, that's a lot of passes over the same "Trigger.new."
  • No, it's not very "readable" to have every imaginable thing that could ever need to happen to a given Contact record in "Trigger.new" in one big "method" separated by nothing but "if newc.a == m, do x; if newc.b == n, do y; if newc.c == d, do z..." with nothing but comments and whitespace to help you keep track of what's responsible for what.  But my my my, does it feel good to get those "CPU Limits Exceeded" numbers down.

 

So ... devs who prefer monstrous one-pass-over-"trigger.new"-per-object-if-you-have-anything-to-say-about-it style but work in HEDA orgs ...

 

What has your response been?

 

  • Get over yourself and do a highly modular version of TDTM as demonstrated in the documentation?
  • Bend TDTM to your will by having it never call more than one "helper" per object?
  • Some sort of hybrid?

 

CC @Nonprofit Hub 

14 risposte

We have two contacts who are in a relationship and living together but are not married. Would it be better to put them under the same Household account under SF or just mark that they have a relationship and keep the accounts separate?

@Nonprofit Get Started Hub
2 risposte