Timeline for Alternate of Protected Custom Settings In an AppExchange Managed Package for Large Configuration Data
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2021 at 12:00 | history | tweeted | twitter.com/StackSalesforce/status/1352586847541735429 | ||
| Jan 22, 2021 at 11:17 | vote | accept | Ashish | ||
| Jan 22, 2021 at 11:03 | answer | added | Phil W | timeline score: 2 | |
| Jan 22, 2021 at 10:58 | comment | added | Phil W | I guess you could hold the data in a regular custom object as long as the stored value is explicitly encrypted and decrypted by the Apex code that manages/uses it. The encryption key could be a single value you store in a protected custom metadata type instance. | |
| Jan 22, 2021 at 9:00 | comment | added | Peter Noges | It’s usually possible to contact Salesforce to purchase additional additional data storage. You could try that. Or perhaps someone else on SFSE knows of a (secure) alternative that works nicely with managed packages. | |
| Jan 22, 2021 at 9:00 | comment | added | Phil W | If you're not able to use named credentials this is quite a knotty problem. Protected custom metadata type records sprang to mind, despite the awkward way you would have to manage these, but these are just as limited with only 10 million "characters" of storage available to your managed package (actually, in total reading how things are counted). | |
| Jan 22, 2021 at 8:46 | history | asked | Ashish | CC BY-SA 4.0 |