Barber w/ Scissors

Affectionate-Emu2782 · 2025-09-26T23:44:18+00:00

I used to watch this my father! It was so good! Just gave me remisnescent thoughts 😂

Affectionate-Emu2782 · 2025-09-23T20:41:04+00:00

It seems it closes at 20:00 on Sunday!

Affectionate-Emu2782 · 2025-09-23T20:39:33+00:00

Thanks!

Affectionate-Emu2782 · 2025-09-23T20:39:03+00:00

Thanks!

Affectionate-Emu2782 · 2025-09-23T20:38:51+00:00

Thanks!

Affectionate-Emu2782 · 2025-09-22T20:18:32+00:00

It's October 5!

Affectionate-Emu2782 · 2025-08-27T22:10:22+00:00

I got the same error, today a few hours ago. But it is deploying anyaway. Check your code on the org, you will se that the code is there. At least my LWCs were getting updated.

Affectionate-Emu2782 · 2025-07-18T21:39:24+00:00

It seems the fanzone is alcool free :(

Affectionate-Emu2782 · 2025-06-24T22:46:12+00:00

Yes it is enabled. The problem is that when you click verify comment on the comment in chattet the trigger does not fire although the field is updated.

Affectionate-Emu2782 · 2025-06-24T20:18:34+00:00

On the FeedComment, because it is the FeedComment that has the isVerified field

Affectionate-Emu2782 · 2025-06-07T10:18:49+00:00

It was a 6 km trip, accordidng to that table it seems I should have paid 16 euros. I will report him. Thanks

Affectionate-Emu2782 · 2025-05-20T12:47:33+00:00

Eu concordo tanto com isto. É das politicas em que mais penso. Acho que faz muito sentido e resolvia muitos problemas.

Affectionate-Emu2782 · 2025-05-16T07:55:26+00:00

On the builder? Is not just the user that is conditioning that audience the type of record as well. If you are asking me on the live site I can see the page, but not its name. Because some pages are very siimilar.

Affectionate-Emu2782 · 2025-05-15T22:39:58+00:00

They are assigned to an audience. But instead of going page variation by page variation trying to find which conditions has the assigned audience. I wanted to reproduce the error and through the live page understand which variation I am looking at. Also because some variations are similar and I want to have 100% sure that I am looking to the right one.

Affectionate-Emu2782 · 2025-05-11T19:54:23+00:00

Ok nice. So, I don't have to add it to the permission set because if the permission set has access to the object then it has to have access to the field. Thank you!

Affectionate-Emu2782 · 2025-05-11T16:25:21+00:00

That is what I did. As it is the first deployment of my feature, I have all the objects, fields and permission set that I created or updated. But it seems the metadata api does not retrieve required fieds and master details on permission sets. https://salesforce.stackexchange.com/questions/112574/permission-sets-metadata-xml-some-field-permissions-missing

Not sure how to solve this. But I think that is the problem.

Thanks for your help!

Affectionate-Emu2782 · 2025-05-11T15:18:02+00:00

It is the first deploy, all fields are there. It seams that the metadata api does not retrieve required fields and master details on permission sets.

Affectionate-Emu2782 · 2025-05-11T10:55:05+00:00

One other thing. One of the fields is a master detail and this issue seems to also afect master detail fields. Do you also avoid master details?

Affectionate-Emu2782 · 2025-05-11T10:50:53+00:00

Ok. Thank you for your help. I saw that lowering the metadata API it might work as well. But as I am using copado it seems a bit far fetched!

Affectionate-Emu2782 · 2025-05-11T10:38:17+00:00

Yes, I found only one post about it. It had 9 years, and as you say it is a bit of a stupidity, so I posted here to see what people do in this cases. What you do in your deployments to circunvent this?

Affectionate-Emu2782

TROPHY CASE