Welcome to the Alteryx Knowledge Base

GCSE-747:The Dynamic Input tool with a DCM connection using the "Modify SQL Query", the "Replace a specific string" seems to be targeting the "Connection ID" attribute instead of the "Query"
user

Created/Edited - 4/28/2026 by Josh Pham | Alteryx

Summary
The Dynamic Input tool with a DCM connection using the "Modify SQL Query", the "Replace a specific string" seems to be targeting the "Connection ID" attribute instead of the "Query" and the "Update a Where Clause" seems to be impacted as it does not show any WHERE clauses to update.
Environment

The Dynamic Input tool with a DCM connection using the "Modify SQL Query", the "Replace a specific string" seems to be targeting the "Connection ID" attribute instead of the "Query" and the "Update a Where Clause" seems to be impacted as it does not show any WHERE clauses to update.
 

  • Alteryx Designer
    • 2022.1
  • Dynamic Input tool
  • Data Connection Manager DCM

 

Steps to Replicate

  1. Add a Dynamic Input tool

  2. In the Dynamic Input tool configuration > click Edit

  3. Check on “Use Data Connection Manager (DCM)

  4. Set up a Connection

  5. Select Data sources > choose a supported DCM type of connection such as SQL Server ODBC

  6. From the Connection Manager > select your saved SQL Server DCM connection

  7. For the Credentials Connections > select Connect

  8. Either in the Visual Query Builder or the SQL Editor > build your query with a where clause

  9. For Modify SQL Query > click Add > select “Replace a Specific String” - the “Text To Replace” shows a "Connection ID" attribute instead of the "Query."
     

  10. For the Modify SQL Query > click Add > select “SQL: Update WHERE Clause” - the WHERE clause does not show and is blank

Cause

The "Replace a specific string" seems to be targeting the "Connection ID" attribute instead of "Query" and the "Update a Where Clause" seems to be impacted as it does not show any WHERE clauses to update.

Defect GCSE-747
Status: Open

Resolution

Defect GCSE-747 is targeted to be fixed in a future release.
 

Workaround A

 

  1. Not use Data Connection Manager DCM for the data source

 

Additional Information
Was this article helpful?