#Nonprofit42 discussing

Hi Vikrant, autocomplete="off" isn't supported directly by lightning-input-field because it doesn't expose the underlying <input> element's autocomplete attribute. 

If you need to control autocomplete, you can use lightning-input instead of lightning-input-field and set: 

<lightning-input
    type="text"
    autocomplete="off"
    name="myField">
</lightning-input>

If you need to keep lightning-record-edit-form and lightning-input-field, you generally can't reliably disable the browser's autocomplete through the component attribute. 

If you can share which field you're trying to disable autocomplete for and what browser you're testing in, I can suggest a more specific workaround. 

Hi Patrick,

Could you share the exact HTML error message you're getting and the type of email template you're creating (Lightning, Classic, or Visualforce)? 

If possible, also share the HTML/code you're trying to save and a screenshot of the error. The solution can depend on the template type and the specific HTML being used. 

With those details, someone should be able to pinpoint the issue. 

Hi Adam,

The custom field mapping is applied when NPSP creates an installment Opportunity from the Recurring Donation. 

So if Installment Opportunity Auto-Creation is disabled, NPSP won't automatically create the next installment just to apply the mapping. If an Opportunity is later created by an external donation platform, the Recurring Donation → Opportunity custom field mapping would not automatically populate that Opportunity unless the integration/process creating it explicitly applies the value. 

Also, updating the Recurring Donation doesn't simply copy the value to every historical/closed Opportunity. NPSP's behavior around existing open installment Opportunities can update mapped values depending on the Recurring Donation processing/configuration. 

For an online donation platform creating the Opportunity directly, I'd recommend checking the integration's field mapping or automation rather than relying on the NPSP Recurring Donation mapping. 

I know this is a very old question, but just in case it helps someone. The External Data Source should first be granted to the individual user via permset/profile. That is all it meant by the bolded line. 

User should now see a banner they can follow to authenticate with that data source, or otherwise follow. 

If you get to the point where you are seeing an error like this

• AllSites.FullControl
• EnterpriseResource.Write
• MyFiles.Write
• Sites.Search.All

if you add all those, then resync the external source metadata and try again it should work

Hello Sean, 

From what I understand, this doesn’t sound like a universally published Salesforce policy where a customer must buy 10 additional UE licenses for an Org Swap. Historically, Org Swaps have generally been handled based on the customer’s existing licensing and commercial agreement, with the replacement org being provisioned to match the appropriate licenses. So if another nonprofit completed an Org Swap in June without this requirement, I’d definitely ask the AE/VP to point to the specific current policy or documentation that requires the additional 10 licenses. It could be a specific provisioning or commercial constraint for this particular account rather than a blanket Salesforce policy, but I’d be interested to hear if others have seen this recently. Hope this helps!

Benefit schedules can be a tricky beast to get your head around in Nonprofit Cloud. The Program Management Implementation Guide is certainly worth having to hand, although practical examples can sometimes make more sense than documentation alone. The Trailhead modules covering attendance and benefit tracking should help with the fundamentals. I think the most important part is understanding how benefit schedules connect with programme participation and outcome measurement. There is a dedicated Trailhead module covering attendance and benefit tracking in Nonprofit Cloud that should address the core questions. If you are still stuck afterwards, similar Trailblazer Community discussions may also offer useful screenshots and examples.