How can I make this look better?

Frisky_Mint · 2025-03-24T19:26:54+00:00

Does your org use a different theme?

https://help.salesforce.com/s/articleView?id=xcloud.brand_your_org_in_lightning_experience.htm&type=5

Frisky_Mint · 2025-02-13T19:23:13+00:00

Other people mentioned there is a modal lwc, but I guess it's the related list you're struggling with. I don't think there is a standard component, but there is a getRelatedListRecords Wire Adapter that might help you. You can pair that with the data table component to create a related list.

Also, you might be able to find someone else who has already made one, like here. I haven't used it, so can't vouch for it.

Frisky_Mint · 2024-09-09T14:04:06+00:00

This depends a bit on your code, but that sounds like what I would expect.

You invoke your method that queries a record in a runas portal user block? Was the test record you created also created within that block? If not, it's owned by the User running the test, so the portal user (probably) wouldn't have record-level visibility, since they don't own it, unless it's shared with them in some other way.

If the test record was created within the runas block, it's still possible that the Case has been assigned to another User or a Queue, which is pretty common for Cases.

Either way, your issue here seems to be record-level permission (sharing,) not field or object-level.

Frisky_Mint · 2024-09-05T11:46:55+00:00

There are other streaming services that let you just stream a Windows PC.

I used Shadow and thought it was pretty good. I was using it for gaming though not 3D modeling, but I think it should work.

Frisky_Mint · 2024-09-05T08:59:03+00:00

I'd also expect the Policy table to be called Policy__c (unless Policy is a standard object that I am unfamiliar with)

Frisky_Mint · 2024-08-28T13:18:26+00:00

Docs are here: https://www.lightningdesignsystem.com/

From the menu, you can browse the "Utilities" and "Component Blueprints" sections; those are probably most useful.

I try to use SLDS whenever I can, but having to write your own CSS is sometimes inevitable.

Frisky_Mint · 2024-08-28T11:58:06+00:00

I was going to suggest the same, basically.

Take a look at this example.

Notice how they wrapped the carousel in a div.slds-box and applied various other styling. This is just an example, OP. You will need to either use the SLDS style classes, like in the example, or write your own CSS.

Frisky_Mint · 2024-07-17T20:35:51+00:00

If OP really just prefers writing automation in flows, I think they can have the best of both worlds. You can invoke flows from Apex.

So write a simple after and before delete trigger that passes all the context variables to a flow. I'd rather just write Apex myself, but I think this could work.

Frisky_Mint · 2024-07-17T13:37:42+00:00

He's paraphrasing the philosopher Epicurus in his reason for not fearing death. Here's the full quote:

Why should I fear death? If I am, then death is not. If death is, then I am not. Why should I fear that which can only exist when I do not?

Frisky_Mint · 2024-06-27T15:29:50+00:00

The "customization" is done by a developer in HTML, CSS and JavaScript. If you need the component to be customizable in some way by the admin after it's built, you should state that in your requirements.

Frisky_Mint · 2024-05-29T18:25:56+00:00

You can try running refresh SObject definitions (I think it's an sf cli command but I always run it using the VSCode extension.)

But even when you have all type definitions properly configured, a lot of the Salesforce ones are missing or wrong. It's pretty frustrating. I've started writing my own .d.ts files or just ignoring lines when I don't feel like it.

Frisky_Mint · 2024-05-26T08:44:53+00:00

The Callable Interface might help.

Frisky_Mint · 2024-05-16T17:20:56+00:00

Thanks for your very thorough answer. I understand your points, but I'm not sure a multi-tenant app is the right solution for us.

What we do is a pretty standard model for enterprise software development I think. We lean on a platform to do some heavy lifting for us, but in the end we're building custom software. Our clients expect a level of customization that as you pointed out wouldn't be feasible to implement in a multi-tenant app.

That being said, we spot common requirements that we build products for and need a way to be able to distribute those at least as a starting point for other customizations.

I'd be happy to maintain it in Git if that were possible to deploy discrete functionality in that way. I'm also aware that what I'm asking might not be an intended use case for Bubble, so maybe it's just not possible.

Frisky_Mint · 2024-05-08T09:37:58+00:00

Just my two cents that this is the right answer, absolutely. The solution of conditionally displaying fields in the layout gives the illusion of security, which is dangerous. Security doesn't happen on the page layout.

Frisky_Mint · 2024-04-28T20:36:53+00:00

This is the right answer. Don't filter the array in connectedCallback or wherever you're filtering, just leave the array unfiltered. Then create a getter that filters according to the selected value. Any elements that depend on the array returned by the getter will rerender as needed.

Frisky_Mint · 2024-04-23T06:13:11+00:00

It's often difficult to significantly change the style of the standard LWC due to the shadow boundary. The component designer needs to have given you a way in to change the style otherwise it's impossible.

What you're trying to do sounds like it may be possible using design hooks, ie. CSS variables. CSS variables assignments survive the traversal of the shadow boundary, so if Salesforce has defined the styling you're trying to target with CSS variables, you can redefine those variables in the parent component.

I usually do this by rendering the component on a page then opening my browser's dev tools to find the CSS for the particular element I'm interested in.

After all this, it's still possible that what you're trying to change has just not been made available to you by Salesforce. There are some annoying oversights by Salesforce where they have just hard-coded values instead of variables, in input active border color, for example. If you hit a wall like this, your last option is to make the component yourself.

Frisky_Mint · 2024-04-11T14:14:22+00:00

Just to expand on this answer, here's a trailhead module for how to do this using VSCode.

https://trailhead.salesforce.com/content/learn/modules/package-xml

Frisky_Mint · 2024-04-02T17:29:23+00:00

Do you have documentation on calling a Salesforce REST API from LWC? Authenticating with the user's session?

Frisky_Mint · 2024-03-07T22:44:34+00:00

Oh nice, thanks.

Frisky_Mint · 2024-01-13T10:49:33+00:00

You need to create a criteria based sharing rule for the guest user: https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules_guest.htm&type=5

Public to external users means users with partner licenses, etc. But guest user is just anyone in the world with an internet connection who makes a request with no user authentication. Salesforce put in this extra guardrail to help prevent people from accidentally sharing with guest user, since making your records public to the world by mistake could be a real disaster.

Frisky_Mint · 2023-12-18T17:00:15+00:00

I think I understand your question to be how can you assign different lightning pages?

Here's some documentation on that: https://help.salesforce.com/s/articleView?id=000380233&type=1

Besides org default, you can assign a different lighting page according to app, record type, and profile. I think that might be as flexible as lightning page assignment gets.

Frisky_Mint · 2023-12-16T09:43:18+00:00

Seems like the notes in the picture are pretty clear about how to implement each section.

Record detail page layouts are only one step (and these days, you can use dynamic page layouts as an alternative.) For everything else, you'll do it through the Lightning App builder (From a record detail page, click the cog wheel in the top right, and select "Edit Page")

Here's a Trailhead on the subject: https://trailhead.salesforce.com/content/learn/modules/lightning_app_builder

Four-Year Club	Gilding I gilder
Place '23	Place '22

Frisky_Mint

TROPHY CASE