A related list can highlight open opportunities on the account , for those people who find it too much work to look themselves to make it easy to see them. Recently a power user raised the need for finding open opportunities for other accounts within the hierarchy. So we built a screen flow to do this

It was fairly straightforward, thanks to the relatively recent addition of the IN operator for get elements.

It does require a get element in a loop, which is generally bad form but should be fine in this use case, as we are in a screen flow and you would need a 99 level deep hierarchy to hit the 100 query limit.

There are probably other ways to solve this, but the key for me was to realize I must first navigate to the top of the hierarchy (via the get in the “loop”) and then work my way down, level by level, adding all the child account IDs to a collection variable. A final query...

solved an interesting question on ohana slack asking about how to display the files attached to a related record in a “legacy” approval process page.

you can do this using a flow datatable, but there are some tricks required for making a clickable link to the file.

salesforce files have 3 objects, and they dont always play nicely

a) content document : this is the file preview page when you are looking at a file. IDs start with 069

b) content version : these are the file versions, and IDs start with 068

c) content document link these allow the many to many relationship to connect one content document to multiple records. i dont know what the Ids start with …

here is the full flow.

here are the details on how to build it

to start, you must create an input text variable in your flow named recordId. this will be populated automatically when you add the flow to a record page.

...

after a long long time created a new support process in sandbox, and of course you cant deploy standard picklists with change sets.

if i had used devops center i would prob be sorted, but I would have to redo everything. i found it to be too much overhead to deal with for what we needed, and havent played with it recently.

so instead, i did the following

1) include the support process in the change set

• make sure your change set includes the record type associated with the support process.
• then click ‘view / add dependencies’ and you can select the support process to include it. thats the only way to get it

2) retrieve case status via metadataapi / workbench

create a file named package.xml and include this and only this

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>CaseStatus</members>

stumbling in the dark…found a path

option 1 - this works

• create integration user – user license = salesforce integration – profile = minimum access - api only integration
• assign permission set license from user page (permission set license assignments -> edit assignments - salesforce api integration)
• create permission set (no license type)
• set object access and field access in perm set
• assign perm set to user

option 2 - this is supposed to work, but would not for me

• create integration user – user license = salesforce integration – profile = minimum access - api only integration
• create permission set with license type = salesforce integration
• assign permission set to user
• create permission set (no license type)
• set object access and field access in perm set
• assign perm set to user (error)

i am unable to assign a perm set that grants access to standard objects to the users, even...

in preparation for a user group session with peter churchill re extending flow with http callouts and lwc for a dc user group meeting, i tested http callout and external services against the petfinder api, developer.trade.gov consolidated screening list api, and the boldsign api. my notes and observations re http callout and transform element are below. peter figured out a bunch of cool things

One of the first decisions to make is whether to use http callout or use external service. My conclusion is that if the endpoint provides an open api spec, it is easier to create an external service and select the methods you need in the flow, for the following reasons:

• when you create a http callout action, you paste in the response and then salesforce parses it. in this process, you have to go through and manually set the types (string, date, boolean, etc) for any properties that the...

I couldnt find any clear documentation on how to get cases to just not be total crap in lightning. Tried many times, and failed miserably. finally found a way through lots of googling, and piecing things together. the short answer is that you need feed filters and a console app and then there is hope.

“Enable Case Feed Actions and Feed Items” in support settings

• otherwise you may find odd stuff with things not showing up in the case feed esp on old cases

setup case feed filters

• can setup feed filters in classic, to determine what is on the page
• feed filters only show up in console apps in lex, but actually make it usable. you can see all the emails, and easily move from one to the next. other normal things

try “Enable Unread/Read on Compact Case Feed” - no idea what that does yet…and maybe ‘enable draft emails’ cuz why not.

create a console app, then do normal lighting...

TIL that you can create custom report type on entity definition + field definition to report on your fields!

h/t : https://www.asagarwal.com/how-to-report-on-objects-and-fields-defined-in-salesforce/ and Anna Loughnan

However I could not include field help text, though it is listed in the tooling api docs for fielddefinition

then i tried a custom report type on entity definition with entity particle, and added field definition via lookup

this worked in theory - i could include description and inline help text.

but when i ran the report, field description remained blank. other folks said the report type worked for them, so i should test more as the report types would be really simple to use. so try that first.

instead I ran a soql query to test it out, and this works

select entitydefinition.label, inlinehelptext,fielddefinition.description,fielddefinition.label from...

changes to configuration, like updating picklist values, can easily mess up salesforce reports, which is a perennial problem for yours truly. i think sometime in the middle ages i dealt with this using eclipse but only vague memories remain.

working today on using vscode to deal with this…first I needed to get all reports locally.

this post on dev forum suggested a nifty package generator extension

I used that extension to generate the package. check the “report” metadata type and it crunched through all 6k(!) reports we have and created a package.xml file

then i could easily retrieve all reports by right clicking on the package.xml file and selecting “retreive source from org using manifest” in vscode!

i then used find/replace in folder to update the old picklist value to the new one! but if I then use force:source:push it deploys all reports, not just the modified ones.

I...

edit : looks like the link in the sandbox refresh success email already has the right url to allow you to login with username and password.

file under stupid workarounds that cant possibly exist in a 50B platform

if you use single sign on in prod, and block login from login.salesforce.com because security and all, refreshing sandboxes becomes a stupid pita because the new sandbox inherits the ‘block login from’ setting,

therefore after refresh is complete, you click ‘login’ in the sandbox list from prod, and it takes you to the direct url to login (ie cs13.salesforce.com)

enter your pwd and you get this helpful message

Please check your username and password. If you still can’t log in, contact your Salesforce administrator.

To fix this, you have to manually craft the mydomain url for your sandbox. this is formatted as

prodMyDomain–sandboxName.sandbox.lightning.force.com

in my...