Skip to content

Storage of custom fees should use discrete names #44

@damienwebdev

Description

@damienwebdev

Is your feature request related to a problem? Please describe.
I'm trying to report on custom fees with JSON_EXTRACT in MySQL, however the data is stored in JSON like:

{"_1748965817694_694": {"code": "my-fee", "type": "percent", "title": "My Fee", "value": 12.5, "percent": "25", "base_value": 12.5, "show_percentage": true}} 

Maintaining the value of _1748965817694_694 in any reports I write is painful.

Describe the solution you'd like
It would be nice if instead this key were the code.

Describe alternatives you've considered
N/A

Additional context
N/A

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

Status

In progress

Relationships

None yet

Development

No branches or pull requests

Issue actions