Routine is compiled and working called EDWGetChangeDate and should accept value of 'dummy' and return a datetime value. Test works.
A Fact Job declares the following Parameters:
Parameter name: changeCaptureDate
Prompt: Change Date
Default value: EDWGetChangeDate('dummy')
ODBC task in the Fact Job has following SQL Code in Outputs/SQL Query tabs
(so.DateUpdated > '#changeCaptureDate#'
or s.DateUpdated > '#changeCaptureDate#'
In production the job changes #changeCaptureDate# into a datetime value and inserts it into the SQL which works.
In development the job changes the value to 'EDWGetChangeDate('dummy')' as if it is a string value, not a routine to run.
I have compiled the Fact job and Routine on the development server. Any idea's why this would NOT see this as a routine to decode and instead sees it as a string of text?
This topic has been locked.
1 reply Latest Post - 2008-05-22T20:00:49Z by SystemAdmin
Pinned topic Job not decoding Routine correctly. Works in production, not in test envir
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2008-05-22T20:00:49Z at 2008-05-22T20:00:49Z by SystemAdmin
SystemAdmin 110000D4XK160 PostsACCEPTED ANSWER
Re: Job not decoding Routine correctly. Works in production, not in test envir2008-05-22T20:00:49Z in response to SystemAdminThe answer is in the calling sequencer. The paramater has to be set in the calling sequencer, and properties of the parameter have to be set to DS ROUTINE by clicking the value, then '...' button twice. Once set this way, it works. Hard to find, no documentation that I can find about it...but it works.