In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

Upgrading version from 2.5.4.Final to 2.6.1.Final for connector configuration
"transforms": "unwrap,RenameField,route",
"transforms.RenameField.renames": "schema.table.PSDSC#:schema.table.PSDSC_,schema.table.PTDSC#:schema.table.PTDSC_,schema.table.PGIVF#:schema.table.PGIVF_",
"transforms.RenameField.type": "org.apache.kafka.connect.transforms.ReplaceField$Value",
"transforms.route.regex": "([^.]).([^.]).([^.]).([^.])",
"transforms.route.replacement": "avro_topic_schema_tablename",
"transforms.route.type": "org.apache.kafka.connect.transforms.RegexRouter",
"transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",

ending up issues as below
2024-05-08 14:40:04,232] ERROR Producer failure (io.debezium.pipeline.ErrorHandler)

Wed, May 8 2024 8:10:04 pmcom.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'PSDSCschema_table'.

Wed, May 8 2024 8:10:04 pm at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:259)

What Debezium connector do you use and what version?

SQL Server connector with 2.6.1.Final version

What is the connector configuration?

SQLServer Connector configuration to replace invalid coulmn names to valid names and sink to kafka

"transforms": "unwrap,RenameField,route",
"transforms.RenameField.renames": "schema.table.PSDSC#:schema.table.PSDSC_,schema.table.PTDSC#:schema.table.PTDSC_,schema.table.PGIVF#:schema.table.PGIVF_",
"transforms.RenameField.type": "org.apache.kafka.connect.transforms.ReplaceField$Value",
"transforms.route.regex": "([^.]).([^.]).([^.]).([^.])",
"transforms.route.replacement": "avro_topic_schema_tablename",
"transforms.route.type": "org.apache.kafka.connect.transforms.RegexRouter",
"transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

This database is on-premise and running MSSQL version 2019

What behaviour do you expect?

With version upgrade to 2.6.1.Final expect it to working as with 2.5.4.Final

The issue with 2.6.1.Final here is related to invalid column name renaming, where columns with invalid names(ie-with symbols ) can't be replaced to something valid in connector confirguration as before . See the config info above

What behaviour do you see?

Issue with replacing invalid column names to the valid names

Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

Yes issue is found in latest source base

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

Yes, attached

How to reproduce the issue using our tutorial deployment?

Set up Onpremise mssql server create cdc tables with invalid columns, add debezium connector config in 2.6.1.Final Version, in the connector config using SMT try to replace invalid column names with valid ones and you see the issue for not getting replaced.

Note: In debezium community, the issue suspected was related to  DBZ-7359