Jonathan Gillespie

I love this idea, it'd be great to see if it's feasible to get this working (and hopefully it won't take 3 years 😆 ). I looked into the Tool...

The code should also added field-level checks for isAccessible, etc

Hi @aneeshbab - in theory, I think it should work in a record-triggered Flow. Could you share more details about your use case? If you're able to share a screenshot...

@surabhipriya29 and @hwong103 apologies for the late response! I believe that @surabhipriya29 is correct, your profile will need the permissions "Customize Application" ([source](https://help.salesforce.com/s/articleView?id=sf.custommetadatatypes_ui_populate.htm&type=5]). I'm hoping to spend more time on...

@ssk42 I would _love_ a contribution for this! I had hoped to work on this a while ago, but the issue has been open for over a year 😅 If...

@jefersonchaves yeah, the idea is to add Apex invocable actions that can by used in Flow to `put` and `get` cache values. I meant to add details to the description...

@jefersonchaves I agree that having 4 classes per data type is a lot of classes, but it feels like the more intuitive & scalable approach overall. My concerns with the...

Hi @PawelWozniak I'll be sure to address those topics in the documentation. For now, here are some answers to your questions: > Could you please add short documentation about the...

Hi @heapallocation - when you're deploying, are you deploying your own metadata? Or are you including the class `LoggerEngineDataSelector` in your deployment? That class is difficult to get full code...

@mGrad10 is this issue happening for you when deploying to a production org? And when deploying, are you only deploying Nebula Logger's `core` directory? The current challenge with those 2...