New Feature Summary
Currently, developers frequently need to tie rich transaction data (such as raw JSON integration payloads, large XML packets, or debug CSV files) to a specific LogEntry__c record. While Nebula Logger easily logs string properties, string fields are strictly limited by Salesforce's field data limits and text area sizing.
Storing exceptionally large blobs within long text area fields can lead to truncation issues. Furthermore, downloading a physical, properly formatted file directly from the Salesforce Files related list offers a much cleaner user experience for administrators diagnosing complex errors.
New Feature Summary
Currently, developers frequently need to tie rich transaction data (such as raw JSON integration payloads, large XML packets, or debug CSV files) to a specific LogEntry__c record. While Nebula Logger easily logs string properties, string fields are strictly limited by Salesforce's field data limits and text area sizing.
Storing exceptionally large blobs within long text area fields can lead to truncation issues. Furthermore, downloading a physical, properly formatted file directly from the Salesforce Files related list offers a much cleaner user experience for administrators diagnosing complex errors.