Hi,
It appears that this issue is related to a limitation within the graphical mapping node. When attempting to create the mapping manually inside the node, I encounter an error indicating that the field name is not handled correctly.

When using a JSON schema, the "#" character in the field name does not raise any issues during development in the toolkit. However, the problem only becomes visible during deployment, which suggests that the runtime validation behaves differently from the design-time validation and may enforce stricter rules.
As a possible workaround, you can bypass the graphical mapping node and use ESQL instead. For example:
SET OutputRoot.JSON.Data.after."field#" = InputRoot.JSON.Data.after."field#";
This approach allows you to explicitly reference the field name, including the special character, without triggering the same error. This worked in my test.
I hope this helps. Let me know if you run into any other issues.
Kind regards,
Kim