Topic
1 reply Latest Post - ‏2008-05-22T20:00:49Z by SystemAdmin
SystemAdmin
SystemAdmin
160 Posts
ACCEPTED ANSWER

Pinned topic Job not decoding Routine correctly. Works in production, not in test envir

‏2008-05-22T13:59:17Z |
Details:
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
Type: String
Default value: EDWGetChangeDate('dummy')

ODBC task in the Fact Job has following SQL Code in Outputs/SQL Query tabs

where
(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?
Updated on 2008-05-22T20:00:49Z at 2008-05-22T20:00:49Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    160 Posts
    ACCEPTED ANSWER

    Re: Job not decoding Routine correctly. Works in production, not in test envir

    ‏2008-05-22T20:00:49Z  in response to SystemAdmin
    The 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.