Issue with Extra Whitespace in Public Tidal Variable
I was actually able to find a workaround for this not using Tidal variables. I ended up hard coding part of the file path in the SQL job which pulls the static string value, and concatenating the 2 strings like this:
SELECT TOP 1 'E:\data\inbound\KMK\RETROACTIVE\' + LTRIM(RTRIM([Data_Date]))
WHERE = 946
When I pass the job output to my ROBOCOPY script it works perfectly.
I'll leave this as answered instead of deleting it in case anyone has the same issue
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...