Perfect, then I suggest you write to AT support and they should be able to solve the issue or tell you if there is a particular option that is causing this.
I’m aware of this bug. Though it’s a strange one. It happens with the Dynamic Data helper of AT. It only happens with that specific field as far as I know.
So my I guess is there is some script running from Bricks that targets that specific field. And I can’t really wrap my head around how to prevent Bricks from deleting the value inserted by my script. Because the value is inserted correctly - Bricks is responsible of deleting it
I understand this is borderline to ask, but I’d suggest double-checking the code from Bricks and share why it could potentially conflict with third-party functions so I can implement a solution.