a good idea - this would provide better visibility and governance

Having this feature is critical because the Budget field is already a native system property used to power the Financials tab, yet it lacks the same search, filtering, reporting, and interaction capabilities as other standard system properties such as Title, Start Date, and Owner. This inconsistency limits users' ability to find, compare, and report on campaign budgets, prevents Opal from accessing the data for automation, and forces teams to create duplicate custom fields that do not provide the same functionality. As a result, it increases manual effort, introduces data inconsistencies, and negatively impacts user adoption and confidence in the platform. Aligning the Budget field with the capabilities of other native properties would resolve a product inconsistency rather than introduce new functionality, while significantly improving usability, reporting, and automation.

this would save me tens of hours of work