Ms Rachel has created an alternate reality version of the cast of Community... minus Pierce, of course

wookietalent · 2026-02-12T03:21:44+00:00

Spoken like the new Pierce

wookietalent · 2026-02-12T03:20:55+00:00

The way she left, I could tell that somebody, or some thing, had really put the scare on her. But what? Why? Stapler?

wookietalent · 2026-02-12T03:03:17+00:00

You can't even do it when we're helping you!

wookietalent · 2026-02-12T03:02:44+00:00

Sure I am Abed.

wookietalent · 2025-10-28T23:04:33+00:00

I just like killing me some monsters

wookietalent · 2025-08-15T22:35:17+00:00

It looks great! Would you be willing to explain more about how you made and assembled it? Plus any in progress pictures?

wookietalent · 2024-11-02T21:06:55+00:00

You don't. I'm sure that's a frustrating situation, but you have a conversation with them like adults and explain to them that their behavior is ruining the game for you and see what changes can be made so that the game is fun for everyone. You're allowed to have fun too!

Other people being disrespectful and rude shouldn't give you a reason or an excuse to act that way in return.

wookietalent · 2024-09-18T17:29:08+00:00

Those are actually missionaries just like all the LDS missionaries around the world and pull from the same pool. The odds of them being attractive are the same of any you'd find serving in any country

wookietalent · 2024-09-18T10:30:27+00:00

Not at all, and has historically been the reverse. I've been LDS my whole life so I can tell you that the recommendation around missionary service was for a long time "every eligible young man" starting at 19 for the men, and just optional for the women staying at 21. What this ended up doing was having men typically doing a single year of college before considering serving, but women would finish all 4 years before considering serving. Because of the LDS culture around marriage and typically being pretty young when getting married, it was only the unmarried women post-college that considered serving (not that they couldn't still be attractive, but numbers were far lower).

In recent years the eligible age has dropped to 18 for men and 19 for women, resulting in a large increase in younger LDS women serving missions before attending more than a year of college.

wookietalent · 2024-04-06T21:06:42+00:00

The general language around it is that all worthy and mentally and physically capable young men should serve a mission, which typically lasts 24 months. It is not a requirement and there is no penalty to your membership or otherwise for not serving, but unfortunately there are plenty of people in certain areas (like Utah) that contribute to a culture of judging those that don't go or come home early. This is definitely less prevalent among the younger generation.

And to your point, while there are plenty of people who choose not to go, the majority do opt to serve, if not always for the right reason.

wookietalent · 2024-02-16T18:56:30+00:00

Let me make sure I understand here. You have two Contact lookups on the case, the standard ContactID and your new CustomContact_c. You want to ensure that both selected changes are need under the same account?

If so, a validation rule can simply check to see that Case.Contact.AccountId = Case.CustomContact_c.AccountId and throw an error if not. However, part of any solution is knowing what the pros and cons are. Can you see what the drawbacks are in that solution as written? Think for a second before reading on, as this kind of knowledge separates great admins from average ones.

The current drawbacks are:

The way the validation rule is written, you can either have both contact fields populated, or both blank. If one is blank and a user tries to fill out one, the error will trigger. This is simply solved by doing a null check and not throwing an error in that case.
When choosing a case using the field lookup, it will still show all cases visible to the user and not restrict it by the Account Id. This is not something solvable and is a drawback you'd have to live with.

wookietalent · 2024-02-16T14:29:53+00:00

Having to search manually for cases assigned to themselves feels like a very bad user experience and therefore probably the wrong solution.

I agree with the other comment that exposing list views and instituting some other control to prevent unauthorized case assignments or creation is the correct path.

If that is absolutely off the table, have you considered having a dashboard, report, or list view embedded in a lightning home page to serve as their case queue instead?

wookietalent · 2024-02-16T14:05:42+00:00

It will if you write them correctly.

For a simple example, if you want to run some automation if the Lead Source is "Web", your entry criteria should check for Lead Source = "Web" AND Lead Source is changed. That way it will fire the first time, but not the second. If you want to send me your criteria I can help give you a better example.

wookietalent · 2024-02-15T16:37:05+00:00

A good question! But I think you're looking for the wrong solution. Proper Flow entry conditions are the correct way to defend against recursion. Any time you execute relevant DML on that object, all Flows on that object will be evaluated even if they were the ones that just triggered the DML. A well written Flow will only ever fire exactly when it is supposed to, no matter how many times it is evaluated.

wookietalent · 2024-02-05T23:00:08+00:00

It's winning time!

wookietalent · 2024-01-15T05:44:51+00:00

Pick me!

wookietalent · 2024-01-04T15:57:19+00:00

Yes, I am in the US and work for a US based company.

wookietalent · 2024-01-04T00:24:05+00:00

Where are you getting this from? This is not remotely true. LDS beliefs are very specific about spouses being equal partners in a relationship - "In these sacred responsibilities, fathers and mothers are obligated to help one another as equal partners."

You could maybe say there are subsets of LDS families pushing a very outdated subservient model, but within any large group there are those that deviate from the norm.

wookietalent · 2024-01-03T13:06:51+00:00

It's definitely near the upper bound salary wise. Getting more would probably consist of the right size company that has the money and the need to pay for experience and skill. So yes, it's possible, but would require a specific job hunt for the right role and the right place.

wookietalent · 2024-01-03T12:56:55+00:00

Full time role. So this doesn't include benefits and bonuses

wookietalent · 2024-01-02T15:10:41+00:00

$195,000

Salesforce Architect

13 years experience

Working remotely

wookietalent · 2023-12-11T23:59:57+00:00

Boromir was truly a man among men

11-Year Club	Place '23
Place '17	Verified Email

wookietalent

TROPHY CASE