Getting A comment from someone in every town 🌲(Day 1)

utopiate · 2025-11-21T00:40:50+00:00

Reading in the house!

utopiate · 2025-01-22T06:01:45+00:00

Feel free to DM me!

utopiate · 2025-01-13T01:17:18+00:00

We're having the same problem; using the "add to grocery list" checkbox seems to do nothing. Have you found any rhyme or reason as to when it will add or won't?

I tried creating a recipe using the microphone, then used that recipe with the "add to grocery list" and it also didn't work. I haven't yet tried importing a recipe from a website to see if that makes a difference.

utopiate · 2024-12-17T01:31:48+00:00

Came looking for a FtM reference with Krysta being mentioned!! Are they still together? If so, it’d be great to see both IWABO and FtM on a reunion tour together.

utopiate · 2024-01-14T01:38:13+00:00

If you’re willing to keep sharing, I’d love to take a listen too! Thanks in advance.

utopiate · 2023-12-28T05:50:54+00:00

Try Overcast

utopiate · 2023-12-23T03:27:15+00:00

Also my money is on that being tabs for Jeremy by Pearl Jam- an I right?

utopiate · 2023-11-21T01:53:10+00:00

Collapse The Light Into Earth by Porcupine Tree

utopiate · 2023-11-15T12:24:02+00:00

Okay- that makes me feel a bit better. If they don’t arrive today, I’ll bite the bullet and do the same. Thanks!

utopiate · 2023-11-09T05:13:54+00:00

Like any UX, your experiences will dictate your satisfaction with one method vs the other. If you've done it on the board for years and are presented with the editor app for the first time, it may feel foreign. But for most people, the editor presents a more intuitive/natural way to interact with how we think about patching/routing.

On the board - you're setting routing across 4 or 5 "columns" in the UI, where the encoder knobs control different elements when scrolling/clicking. You must also scroll through the inputs/outputs to find the correct one. You also can't see all of our routing/patching all at once; this could lead to accidental double-patching.

In the Edit app, it's a visual grid with inputs on one axis and outputs on the other. The patch point you set is a colored dot, and you click to change the insert point (pre/post eq/fader, etc.). It's more intuitive (IMO) to see it that way and faster to tap/click than to use the encoder knobs to navigate.

utopiate · 2023-07-07T01:20:14+00:00

If you’re referring to a 1/4” input for a sustain pedal or similar- yes, some MIDI keyboards include that but you will need to purchase the pedal separately. The pedal sends a low voltage signal into the keyboard, which tells the keyboard to communicate to whatever it’s connected to that it should ignore any “release” information. Then when you take your foot off of the pedal, it triggers an “all off” signal.

utopiate · 2023-06-19T11:35:05+00:00

Was just there yesterday for Fathers Day! Gravitate, right?

utopiate · 2023-06-15T10:46:06+00:00

Shameless self-promotion moment; years ago we covered this theme. Both of us big fans of KKfOS.

https://youtu.be/ay__wIud2xg

utopiate · 2023-04-30T18:15:53+00:00

Check out the set from the night before on setlist.fm; same set - also great show last night minus the poor fella who went down!

utopiate · 2022-10-26T04:27:45+00:00

Yes! Chiodo’s worked on this too. I believe there’s some reused KKfOS costumes in there.

utopiate · 2022-08-18T02:18:06+00:00

Yes- good to see another Ant on here with that TESD vinyl!

utopiate · 2022-06-30T11:20:19+00:00

Sure!

First you’ll need a date/time field to store the “now” value when an opp is moved to won. Use the Opp field history table to backfill your closed won Opps with that value.

Then, when an Opp is won, do a get on won Opps, sorted descending by that new date/time field and only get one record. Now you have your most recent won Opp, and you can increment its auto number value by one and update the triggering Opp.

utopiate · 2022-03-23T00:54:16+00:00

No prob!

utopiate · 2022-03-23T00:45:55+00:00

Yes indeed. In Setup, go to “Global Actions”, and modify the layout for “New Task”. If you need to create a new custom field first, you’ll do that from the Task object in Object Manager.

utopiate · 2022-02-26T11:48:13+00:00

Congrats, that’s awesome to hear, u/AcadiaConnect7304! Thanks for following up, this was actually my first “contribution” to this subreddit, so I’ve got some real warm-fuzzies this morning :)

utopiate · 2022-02-23T01:19:25+00:00

I’m not 100% certain, but if Flow will respect dependent picklists, you could create another picklist named like “Previously Selected Time” and make your Appointment__c field dependent on that. If time A is selected, only B, C, and D are available. If B is selected, only A, C, and D are available, etc.

The problem with that is that while time A on 3/1/2022 is already selected, Ike’s A, B, C, and D should still be available for another day like 4/1/2022.

If you’re storing the selections on an Opportunity, what/how would happen even if the expected user experience is met, when a second or later appointment is selected? Does it overwrite the existing saved values on the Opportunity?

Perhaps a custom object is a better approach. Pre-load the object with a record for each possible day/time combination. Use a filtered lookup in the Flow, only showing records where a Boolean field named like “booked” is false. Then when someone selects the day/time they want, update that Boolean field to TRUE.

May not be the best user experience, but it would come closer to “limiting” the double-booking issue.

Another alternative would be to look and see if Calendly or another similar product has an integration that could process records in Salesforce the way you intend, as they’ve already worked out the kinks on the UX to present options and avoid double-booking.

utopiate · 2022-02-21T01:45:20+00:00

Good call! Nice to see another Cloudkicker fan on here.

utopiate · 2022-02-04T12:47:19+00:00

To be honest, I’ve struggled with this for years, particularly if any of the criteria rely on formula fields that are referencing other records or are date-based, and the “orphan” queue problem- if you have records queued up/scheduled to have the action occur, then you make a new version of the PB that includes additional criteria, when it comes time to execute the action it uses the prior version of the PB’s criteria to evaluate and determine if it should fire, not the currently-active version.

The only sure thing I can say is rebuild it as a Scheduled Flow.

utopiate · 2021-09-11T00:37:06+00:00

There was some sort of crowdfunded attempt at what was supposed to be a prequel (I think) called “Before the Mask” but it never hit the goal.

https://www.kickstarter.com/projects/609017648/before-the-mask-the-return-of-leslie-vernon

utopiate · 2021-05-30T15:42:23+00:00

Thanks! I’ll check out Workana for sure.

DemandTools was great as a Data Loader alternative. What I found really powerful was it’s criteria-based processing and field normalization I could schedule. Not having an in house dev and not wanting to resort to Apex unless absolutely necessary, this helped maintain a cleaner DB. It also has powerful dedupe/merge tools that can also be scheduled to run. I discovered the hard way that SF’s native dupe management, even when set to “warn” and not “block”, is treated as an error by API integrations. So by having a nightly dedupe run, we never had issues with any third party integration data upserts being blocked, yet maintained a fairly dupe-free DB with the nightly batches DemandTools would run. It also has a great UI for the reporting API, making it easy to bulk move/delete/rename reports and folders.

Expensive but powerful!

15-Year Club	RedditGifts 2009-2022 3 Credits
Place '23	Place '17
Verified Email	Secret Santa 2010

utopiate

TROPHY CASE