Feed

Hi @240 SRI NIKITHA SAVULA S

, In my case Flow is the one of the Option. I think we can go with flow.  

• A record-triggered flow (before insert) can copy the Account’s Billing State to a custom field on the Opportunity at creation.
• Once saved, the value remains static, even if the Account’s billing state changes.
• Ideal low-code solution for this use case.

this is a common need, and I’ve seen a few good ways to handle it depending on how much flexibility you want. The simplest approach would be to create a custom long text field on the Account object, maybe call it something like "Working Memo" or "Sticky Note." You can then place that field right at the top of the Account page layout or even on a Lightning page in a custom banner area so it’s very visible.

If you want it to stand out more visually, you can use a custom Lightning Web Component to style it like a sticky note or banner. That would let you control colors, font, maybe even add a label like “Attention Note” or similar. Everyone with access to the record could update that one field, so only one memo exists at a time.

Another option is to create a custom object related to Account, like "Account Memo," but restrict it so only one memo can be active per account. That gives you a bit more flexibility with history or future enhancements, but it’s a little more effort to build.

Avoid using Notes or Chatter here—they’re not persistent or obvious enough for what you’re describing. You want something front and center that every agent sees the moment they open the record.

Yeah, this is one of those annoying issues that comes up when trying to include reports in a second-generation package. The error you're getting:

filterlanguage: Invalid value specified: 1

usually means that Salesforce added a value during report creation that doesn't play well with packaging. Specifically, the value 1 for filterLanguage isn't valid for metadata deployments. It often gets pulled in when you retrieve the report metadata from an org.

What’s worked for me in the past is opening the report’s XML file and either changing the line:

<filterLanguage>1</filterLanguage>

to

<filterLanguage>en_US</filterLanguage>

or just removing that line completely. After that, try running the package version create command again.

Also worth noting, reports created through the UI can sometimes include other metadata elements that don’t behave well in packaging. It’s always a good idea to manually review the XML for anything that looks off.

Hey Prat, 

This kind of issue with Data Loader usually comes up due to either a Java problem, system update, or something changing on the network side. Since both users have been using it for a while and it just started happening, here are a few things you can try: 

For the first user who doesn't get a login pop-up, it might be that the login window is either being blocked or opening off-screen. I'd suggest closing Data Loader, deleting the .dataloader folder under their user profile (C:\Users\Username.dataloader), and then restarting it. Also, make sure they’re running the latest supported Java version and try running it as admin. 

For the second user seeing "failed to send request," it sounds like Data Loader isn’t able to connect to the Salesforce login server. That could be due to a proxy, VPN, or a firewall issue. Make sure nothing is blocking https://login.salesforce.com. Also, check that they’re on Java 11 or whatever version is officially supported for the version they’re running. You could also try launching it from the command line to see more detailed error logs. 

If the issue persists, it might be worth reinstalling Data Loader or upgrading to the latest version. 

Hi , 

Try unchecking the checkbox "deselect the checkbox Restrict picklist to the values ​​defined in the value set" in Picklist (Multi-Select) Options in the settings for "Close Reason". 

Hi , 

Please check this article. 

Hi , 

Try disconnecting the current playground and creating a new one. 

How to Disconnect a Playground

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

Hey @Aqub Younus, each superbadge org has unique pre-configured data and metadata needed for that specific superbadge unit. So, 1 org can't be used for all superbadges. Each superbadge unit has the special superbadge org signup link available in the scenario text.

Hey @Nandini Devi Rachapalli, make sure you are using an Einstein org and not a normal trailhead playground org. Also, make sure the Einstein setting is turned on for your org first. 

Follow these steps: 

1. From Setup, in the Quick Find box, enter Einstein Setup, and then select Einstein Setup. 

2. Enable Turn on Einstein and refresh the page.

I agree with your take—setting up a separate Role and Profile for the consultant is the cleaner and safer route. That way, you maintain clear visibility into their actions through the audit trail, and you avoid the messy confusion that comes from shared logins or using "Login As" without proper documentation. 

It also reinforces accountability. If something breaks or changes unexpectedly, you know exactly who made the change and under what access level. Giving them limited access based on the principle of least privilege is always a good practice, especially when dealing with external consultants.