# These warnings will become errors in the future **URL:** \ **Category:** Kinetic ERP\ **Tags:** customization, crying\ **Created:** [August 2, 2024, 5:36pm UTC](https://www.epiusers.help/t/these-warnings-will-become-errors-in-the-future/117505 "2024-08-02T17:36:09Z")\ **Posts on this page:** 1\ **Showing post:** 21
**Author:** ![Evan\_Purdy](https://www.epiusers.help/user_avatar/www.epiusers.help/evan_purdy/32/69101_2.png) [@Evan\_Purdy](https://www.epiusers.help/u/Evan_Purdy)\ **Post date:** [August 2, 2024, 6:09pm UTC](https://www.epiusers.help/t/these-warnings-will-become-errors-in-the-future/117505/21 "2024-08-02T18:09:47Z")
Yeah, a little: > [@Compiler Warning when saving BPM after recent Kinetic updates](https://www.epiusers.help/t/compiler-warning-when-saving-bpm-after-recent-kinetic-updates/111289/10): > > I want to clarify that these warnings are not going away with 2024.1. The warnings are intentional and are highlighting custom code patterns that we have identified as being problematic. The problems include security, performance and data integrity. The set of warnings will continue evolving as we identify more patterns to avoid. The warnings will not stop your code from compiling or running. However, in the future, these warnings will become errors. So do heed them and consider alternatives. > [@System.IO](https://www.epiusers.help/t/system-io/108953/26): > > I’ll be at Insights. You can find me at the Tools booth (or whatever we’re calling it this year) most evenings when I’m not teaching Extended Education or Labs. In the meantime, I’m happy to continue the conversation here. I’ll start with a few notes… The introduction of warnings should be in the release notes. If you can’t find them, let me know and I’ll hit up the docs team for clarification. Using [System.IO](http://System.IO) is not going away as a whole. Picking arbitrary paths, however is what we are limi… --- _[View the full topic](https://www.epiusers.help/t/these-warnings-will-become-errors-in-the-future/117505)._