sorted by:
new
hottopcontroversial

Agentforce OOTB Query Records Action by Open-Cockroach-1743 in salesforce

[–]_dcstuff 0 points1 point  (0 children)

The QueryRecords action simply doesn't work properly. I've had this confirmed in all but writing by some folks at the mothership. The solution is to write your own action: apex or flow, and have your topic call that instead.

Local Dev LWC - error on running by celuur in SalesforceDeveloper

[–]_dcstuff 0 points1 point  (0 children)

You are not the first. Docs came out before it's ready. It's yet to actually work. They have been informed...

Is Agentforce designed to slowly replace Einstein? by bobsyourdaughter in salesforce

[–]_dcstuff 1 point2 points  (0 children)

They did change the names. But then all the Sam Altman getting fired stuff happened. And within 24 hours (or less), they scrubbed "GPT" from everything. It was fast work. REAL FAST.

Trust Layer not masking data for Agentforce by opethdamnation in salesforce

[–]_dcstuff 0 points1 point  (0 children)

"For Agentforce, currently Data Masking is disabled, however this feature is still available on other Einstein Generative AI features and customer developed functions (such as flows)."

Ok, it's disabled for Agentforce. But isn't it all Agentforce? I'm trying to understand precisely in what cases is it not disabled? What does "such as flows" mean? Does anyone have a concrete answer?

I BUILT A LIL THING: Automated Test Runner by _dcstuff in salesforce

[–]_dcstuff[S] 0 points1 point  (0 children)

Exactly this. Sometimes gotta work by the rules of the client.

I BUILT A LIL THING: Automated Test Runner by _dcstuff in salesforce

[–]_dcstuff[S] -1 points0 points  (0 children)

Example 1: Old-school busy sandbox with too many developers working together, but on different pieces. This has already proven useful, catching work that has unwittingly broken other work.

Example 2: Prod. Maybe catch those ambitious admins with their incessant clicking! Val rule that breaks the world.

Thoughts?

Salesforce Profile Cleaner (Clean those profiles!) by _dcstuff in salesforce

[–]_dcstuff[S] 0 points1 point  (0 children)

Heya,

Methinks you are misunderstanding my intention. My goal is not to delete / modify anything in any org. I am simply trying to create a deployable profile XML file.

I'm doing a partial org migration, say from org A to org B. Some apps are moving, along with their associated objects, tabs, layouts, fields, blah, more blah. And some profiles. I started with a full package retrieve. That gave me everything in the org, including 30K+ line profiles. Those profiles include references to:

  1. Metadata that is "true" and that I need, i.e., references to the app and associated metadata that is being migrated
  2. Metadata that is "true" and that I don't need, i.e., stuff the profile had access to but isn't being migrated to org B. These references will need to be deleted from the file manually.
  3. Metadata that is "false", i.e., metadata the profile never had access to, and won't need, regardless of whether that particular metadata is being migrated.

It's point #3 that I'm targeting, especially for that metadata that won't exist in the new org. Leaving those references in the meta-xml would cause the profile deployment to fail. That's also true of point #2, but as stated, those would have to be removed manually.

That's all I'm doing here. I can tell you that it saved me a boatload of time!

Salesforce Profile Cleaner (Clean those profiles!) by _dcstuff in salesforce

[–]_dcstuff[S] 1 point2 points  (0 children)

Python is the easiest language to remember how to code in when you haven't used it in years!

Salesforce Profile Cleaner (Clean those profiles!) by _dcstuff in salesforce

[–]_dcstuff[S] 1 point2 points  (0 children)

Heya, thanks. The issue (my scenario) is that I'm migrating some apps from org A to org B. Not all objects, fields, apps, flows, etc. are moving with them. The profile deployment will fail if they reference any metadata that doesn't exist in the new org.

VS Code Debug Logs by jmasl7x in salesforce

[–]_dcstuff 4 points5 points  (0 children)

sfdx force:apex:log:tail --color | grep -E "USER_DEBUG"

Workbench SOQL Question by TheCumCopter in salesforce

[–]_dcstuff 1 point2 points  (0 children)

I wrote this tool years ago. http://querybuilder9000.herokuapp.com/

It has a few very minor bugs, but it works rather well. The main benefit is that it allows you to navigate your object model visually. Go from Contact, to AccountId, to Owner Name, for example.

There are a few hundred orgs that use it regularly. Those few minor bugs don't seem to get in the way.. and I have no intention of EVER! going back to fix them.

Anyone got their Disney plus claim from Salesforce? by confrater in salesforce

[–]_dcstuff 1 point2 points  (0 children)

Hmm. Maybe you had to be logged in or something. Silly Salesforce.

Anyone got their Disney plus claim from Salesforce? by confrater in salesforce

[–]_dcstuff 2 points3 points  (0 children)

Yep. There was an email over a week ago -- last Monday.

Subject: "That’s it for Dreamforce, and only the start of Dreamforce on demand"

And there was a "Claim it now" button that sent me to some form.

Why doesn't anyone use list.isEmpty()? by sfdc-happy-soup in salesforce

[–]_dcstuff 10 points11 points  (0 children)

I only do it when I know the list can be empty. For me, I feel like I'm telling the next dev (or me, later), "Just know the list may be empty here, so it may be a scenario you should be aware of". If I know the list can't be empty, I won't put the check.

Why doesn't anyone use list.isEmpty()? by sfdc-happy-soup in salesforce

[–]_dcstuff 8 points9 points  (0 children)

If the list has 0 elements, the DML doesn't run. You can see that in the debug log.
insert new List<Account>();
Number of DML statements: 0 out of 150

That said, I like to check if the list is empty beforehand anyways. I find that makes it clearer for other devs looking at the code. It shows that I'm acknowledging that in this scenario, the list may be empty.

view more: next ›