Most likely your connection is using utf8 or your database character set is utf8 (i.e. it can store 3-byte characters) or your default character set for the database is utf8 (procedures use the db character set for string/text parameters if not specifically set).
First, check the connection myDBR uses. See if the mydbr_config.php has a row:
define( "DB_CHARSET", 'utf8mb4' );
Then check the default database for the database:
show variables like "character_set_database";
You can change the character set via ALTER DATABASE-command.
Finally, if your setup uses uf8, you can specify the character set for the parameter via the 'character set' definition. Sample procedure parameter would be:
inParameter varchar(100) character set utf8mb4
And for the demo, myDBR demo database is old enough that it was created before MySQL 5.5.3 which introduced the utf8mb4. The demo db uses still utf8. We'll update the character set for the demo (we've updated the report in question)