Dynamic action filters only work for internal users (admin) but not community view.
Scenario - I am using the dynamic action filters for the conditional rendering of button.
Dynamic Actions are not yet available in Experience Cloud, unfortunately.
There is an idea on the IdeaExchange to add it.
Related
I am trying to use both components in my angular application. I am a backend developper and absolutely newbie in angular. I have been reading the roles and users components in the source code and I think I cloned it for my Customers component. I have guards, defaults and all the code like Roles and Users but, although the code compiles and the API call is done, I have nothing in the screen, only the Total records are displayed. No action buttons, no table rows, no pagination...
Is there anyone who has use these components and can bring me some help?
Many thanks
Those components are needed for customizing built-in modules. Let's talk about Users for example. The Users component is a built-in page and you do not have access to its code. However, you may still need to make some changes like adding a New User button on the toolbar or changing its columns, form fields etc. That's why ABP Framework provides some injection tokens to override/extend/customize these features. Since you are developing your own page, you do not need any of this. You can directly use ngx-datatable in your own component, add or remove columns and so on.
I am a very newbie to SF so pardon my ignorance. I am doing the trailheads and logged into developers org. There I quickly created a custom object with some fields. Now how do I get a CRUD page for the custom object. I have been looking through the documentation and trailheads but I finding everything except this simple step. Can someone please suggest how I can get a CRuD page automatically generated from custom object that I can use to add edit and delete records?
Thanks
You'll need to Create a Tab for your custom object. This tab can be exposed in both Salesforce Classic and Lightning and allows you to create a new record in the object, view list views, and so on.
I am trying to call an external api from salesforce apex class which will get all the products.so next i want to show these products as picklist in salesforce lead creation or edit page.I am not sure its possible or not.Any solution or workaround on these is mostly appreciated.
I don't see a way to do this on a standard layout.
I personnaly could do this in a Visualforce page. Probably you probably can do this in a Lightning page as well.
I want to add multi language functionality on my lightning component.
I am not able to find anything useful.
As now i am able to translate only currency and timepicker only.But i want to translate all the custom label (like in VF pages)..
Interesting. I'm new to lightning although I have extensive experience with Apex and so far the only way I can see this happening is to do a metadata call from Apex to generate the list of custom labels and its equivalent language and consume that that on the lightning component controller/helper via the init event. I can't find anything in the lightning developer guide on how to dynamically do this like in visualforce page.
Hope someone can confirm too.
I have a doubt, i've been working with salesforce for a while and now i have a requirement from a customer.
They need that some custom fields be populated with a value of parent object, making some research on stackoverflow, i found this post, but this isn't working for me because my project is a manage package and when this is installed on a another salesforce instance the id of custom field change.
if someone could help me, I will be grateful.
Thanks!.
I can't see any way of doing the same as that post without using the IDs, I was thinking you could route via a VF page and build up the URL in the controller but it doesn't seem as though you can get the IDs of fields, just their type etc..
I think the best you could do in this instance is to override the default new recordpage with a visualforce page. In the constructor of your controller you could then loop through the page parameters and pre-fill the corresponding fields on the new record before it's displayed on screen. Using fieldsets or just an <apex:Detail> component would keep the level of effort down and also maximise the flexibility of the page for the end users.