New answers tagged

1

If you are not building a Managed package solution, there are a couple of ways you can secure the keys. Use custom objects with a Private Sharing model. Keep OWD Private, this way no one will have access to it except System admin and owner of the record. You can further secure it using the encrypted fields (Note this will not need a shield license). Using ...


1

You can set the default template value in the lighting component itself. When the user loads the record using your component and there is no data in that field just put the default value in the field. Also, you can put that value if it's a new record. To be able to change the default template, without changing the code. Use the static resource to store it ...


1

Custom text fields only support 255 characters. You can try using a rich text area or long text area, but you'll have to use Apex to populate the field before the record is created (i.e as a default value). In particular, you'll need to use a Before Insert Trigger.


1

So the answer to this is in Profiles and not Permission sets. Permission sets are awesome, and you need to include some with varying levels in your packages so admins can easily assign correct permissions to different profiles. But as far as I can tell those permission sets can only be assigned in a script you run after installation. So you need to update ...


0

You can query them all and display them on the custom component using the lightning data table. Aura Datatable | Lwc Datatable


2

For the code completion suggestions to work, it relies on the SObject definitions being refreshed as opposed to whether you've retrieved the new metadata. You can do this by using the Command Palette (CTRL+Shift+P) and running the following action SFDX: Refresh SObject Definitions


3

Salesforce does not "randomly" delete records, not even if you meet or exceed your storage quota (at worst, you would be prohibited from creating new records). You'll want to check for automated processes (Process Builder, Flows, Apex Triggers, etc) that may be deleting these records. You may want to set up some debug logs which could show you which ...


0

The above given solutions works perfectly using Apex Metadata Service (https://andyinthecloud.com/2013/10/27/introduction-to-calling-the-metadata-api-from-apex/); but it requires to import all code for even a small requirement. After, release of Tooling API, I find it lifesaver for such implementation without importing and managing too much code. We just ...


1

Is this occurring in a sandbox as well as production? It would be a lot easier to take additional steps in a sandbox to detect the unwanted updates. These could also be applied in production, but are more likely to have unwanted side effects. You say that Key_Feature__c records shouldn't change. Especially the older ones. I'd use that as a basis for finding ...


Top 50 recent answers are included