Codeless Connect Framework (CCF) Template Help

jamos​  Sorry to hear that. The second trick that comes to my mind is to leverage the pagination attribute in your polling configuration. While not its intended purpose, you can use it to build the required date parameters with proper variable substitution.

"pollingConfig": {
  "request": {
    "apiEndpoint": "https://my.hostname.com/path/to/api/myEndpoint",
    "httpMethod": "GET"
  },
  "queryParameters": {
    "EventDates": "{_QueryWindowStartTime}"
  },
  "pagination": {
    "type": "custom",
    "paginationType": "linkHeader",
    "link": "{_nextPageLink}",
    "additionalQueryParameters": {
      "EventDates": "{_QueryWindowEndTime}"
    }
  },
  ...
}

• The initial request will send the EventDates={_QueryWindowStartTime} parameter, which is correctly substituted from the queryParameters section.
• The pagination attribute is configured to add additionalQueryParameters to the next page request.
• By setting the pagination type to custom and the link to a placeholder ({_nextPageLink}), you effectively bypass the standard pagination logic.
• The additionalQueryParameters section will then append EventDates={_QueryWindowEndTime} to the URL, resulting in a single URL with both repeated parameters properly substituted.