I do this frequently but at least one client has this fault:
I added a new column to a table using a SQL statement, which causes the column to be created and added to every publication that uses this table.
Now I create values by using an update statement:
update table
set newcolumn = oldcolumn
The column and the values are properly replicated from server to server, but at least one client (that uses the same publication) only gets the new column but not the values from the update statement.
The log shows successfully updates of the right number of table rows.
I use SQL Server 2008R2 with merge replication, no filters.