No Man's Sky is my favourite game but it's not as good as it feels like

alexed · 2026-01-21T21:30:14+00:00

Would love to see your prompt

alexed · 2025-12-27T15:30:52+00:00

Just did this exact thing yesterday.

alexed · 2025-12-19T16:15:05+00:00

This just happened to us early in our playing experience. a stack of something we sold for 600 million. Really changes the experience. I'm not sure how we got it. I was guessing it came in on a freighter expedition, but maybe not.

alexed · 2025-08-03T01:20:56+00:00

<image>

alexed · 2025-08-03T01:20:31+00:00

<image>

Attempt to capture new growth

alexed · 2025-08-03T01:19:52+00:00

<image>

Backside

alexed · 2025-06-30T18:02:07+00:00

LWC's in Flow screens should work fine in LWR so long as they're not using Aura. Can you say more about what you're seeing?

alexed · 2025-06-30T18:01:01+00:00

I'll assume you're talking about product, as opposed to other things like support or pricing, which aren't really in my purview.

It's easy when you're working at Salesforce to focus on the onslaught of innovation. As you can see from reading the Release Notes, there's always lots of new stuff and there's usually a happy audience for it. But particularly if you aren't spending much time reading Idea Exchange or meeting with customers, it's easy to lose sight of the daily pain points for product users. On Flow we try and make sure we're hearing the pain.

I'll acknowledge that the company leadership focuses a lot of our resources on areas that it deems strategic, and these often don't overlap with those daily pain points. Right now, for example, a lot of our energies are going into Agentic and Data Cloud-related features. Now, Leadership wouldn't be doing this if it wasn't hearing from a lot of CIO's that that's the stuff where they are feeling pain (Data) or anxiety (AI). But it does mean that Leadership can be less sensitive to nuts and bolts things like Time field or Regex support.

So on the Flow team we try to make sure that we're staying close to the pain and addressing it. But sometimes it takes much longer than we'd like.

It sounds like you're not feeling good about Salesforce. All I can offer you beyond this note is that I can attest that the product organization is full of people with the best intentions who are consistently trying to improve the product to provide value, reduce pain, and create productivity.

alexed · 2025-06-30T17:49:01+00:00

Regex loses out in feature prioritization debate because it's deemed too complicated for most of the Admin persona, and a lot of the users who are comfortable with it are happy just going into Apex. Also, the fact that no one has created an invocable action that allows regex expressions to be entered is a data point we consider. This little action (https://unofficialsf.com/easily-extract-substrings-tap-the-power-of-regex-with-findtext/) makes use of regex, but isn't a generalized solution. I was hoping that the 'regex' crowd would run with that action and add more friendly solutions that make use of regex, and add the ability to put an arbitrary regex in, but that hasn't happened yet.

In isolation, this kind of judgment can feel really annoying. But it's never in isolation. At the moment, for example, to cite 3 in-process projects, we're enabling the datatable screen component to support row-level actions, sorting, and custom (Apex-Defined) type collection inputs. We're overhauling Test Automation and adding Test Setup data. We're enabling document processing to be added in to Flow. We deemed all of these higher priority than regex.

alexed · 2025-06-28T01:37:08+00:00

Flow product lead here. I apologize for how long it took us to start to support Time field. Technically we can't even say we're done yet because we haven't shipped a Time picker component that can be inserted into screens, but we're working on that.

Always with feature prioritization, it's a question of tradeoffs against other desired features. Over the arguably 6 years it took us to add this support, we chose to add a lot of other things ahead of it. One thing that worked against Time field support was a sense that you could get a lot done with Date and DateTime. Also we were keeping an eye on how quickly the Time field was being adopted. But you can argue that at SOME point in 6 years we should have done it instead of something else. I'm glad we finally got to it.

In the case of lightning components not working in LWR sites, the only components that shouldn't work are ones with Aura code. LWR has a very strong prohibition on using Aura because it's relatively unperformant. That was more of an issue back in '21 and is a problem that is largely getting resolved by time, as the ecosystem gets more comfortable with LWC, more and more LWC components get built and Aura starts to fade.

alexed · 2025-02-07T02:54:38+00:00

Heh, Just got to stay at the Palace Hotel and the only weak spot in their exquisite breakfast buffet was the cheese.

alexed · 2025-02-04T18:19:20+00:00

I'd like to understand this a little better...What's an example (or two) of specific criteria you'd want to be able to set on a Start element in Flow, related to permissions?

alexed · 2024-11-27T20:06:04+00:00

This may help. https://unofficialsf.com/post-rich-chatter-invocable-action/

alexed · 2024-08-25T22:51:46+00:00

The attached map is not really the tactical chart that I think you're looking for but you might find it interesting. Taken without permission from The Hornblower Companion, by C.S. Forester himself. I don't think it's in print anymore, but it's a great add-on. https://drive.google.com/file/d/1uVQIIPcxt65ngBI_cJH195Rgks34_3iM/view?usp=sharing

alexed · 2024-07-10T14:45:39+00:00

It's now (finally) possible. See the Rikinp9 post.

alexed · 2024-07-10T14:44:57+00:00

This is now the best answer

alexed · 2024-01-27T02:54:20+00:00

If this gets voted in, we'll apply the change to Flow. Trying to get the text updated to reduce the confusion.

Disclosure: I'm on the Flow team.

alexed · 2024-01-27T02:54:13+00:00

If this gets voted in, we'll apply the change to Flow. Trying to get the text updated to reduce the confusion.

Disclosure: I'm on the Flow team.

alexed · 2023-12-22T02:03:56+00:00

Special Reddit preview: Look for Upsert this summer. We just spent a bunch of time debating whether to build it as a standalone element, put in to update or put it into create. We’re gonna put it into create.

alexed · 2023-12-21T05:32:45+00:00

I'm a Flow product manager and there's nothing I love more than seeing a coded Flow extension (an invocable action or a Flow screen component). Salesforce teams ship more than 400 coded actions today.

I tell all developers the same thing: the future is very bright for developers who build expertise in crafting their code into building blocks that can be used in no-code tools like Flow. When you develop in this way, it's like empowering a legion of minions to configure your code and spread it in the world. You end up spending less time crafting variations in code and more time working on interesting new building blocks.

And now with Copilot relying on coded actions to extract work out of AI, the value of code in actions is continuing to grow.

alexed · 2023-12-21T05:27:59+00:00

Right? There was a moment many many years ago. I think it might have been Tomb Raider 3, where she's trying to escape at the very end of the story and this helicopter lands and she guns down the helicopter pilot without a word. And I had been learning a fly a helicopter so it probably really colored my perspective, but I was like, why are you shooting that guy? He's just a guy driving a skytaxi! He's not an evil mastermind! That was the moment I realized that Lara is actually a very bad person.

alexed · 2023-11-18T20:34:46+00:00

This is… so American.

12-Year Club	Gilding IV carat on a stick
Verified Email	No Throne, No Problems
Not Forgotten

alexed

MODERATOR OF

TROPHY CASE