SSIS thinks an invalid expression is valid

Hot Topic

Object Explorer/Server Explorer Error
Insert Script from one table to another
Error loading Oracle DATE data
cannot install integration services
Possible pass parameters on "Jump to URL" properties?
New to SSIS
using AJAX
SQLAgent running SSIS corrupting offline cubes?
Installation Stalls at "Detecting Installed IIS"
Failed SQL 2005 SP1 installations (Hotifx.exe crashes)

SQL Server

Select between ???
Basic Reporting Problem
Query Notification / SQLDependency fails on table w/ computed column
"Serializing" to the SqlServer Database
Reporting service with sql server 2005
Partition help
FTP Module & Proxy
"product level is insufficient" message during flat file import
Can't connect to SSIS
Is this possible???

SSIS thinks an invalid expression is valid

I have put the following invalid expression:

@[Metadata::ValidStream == TRUE

(note the lack of a closing square bracket) into a precedence constraint, clicked the "Test" button and got the message "Expression validated successfully".

Can anyone replicate this

-Jamie




Answer this question

SSIS thinks an invalid expression is valid

  • CaKiwi

    Well its a bug in IDW16 then cos ....hang on...ITS THROWING THE ERROR NOW exactly as you'd expect!

    I swear on my mother's life when I did that an hour ago it was saying the expression was valid. God this thing annoys me sometimes :)   (Remember the variable properties window issue )

    cheers Darren.

    -Jamie

  • Leandro Ramos

    Tried it on a constrant with the same result, or rather the same error message. Makes sense as the same expression validator engine will be used.

    BTW you can use either "[@User::Var]" or "[@User::Var] == true", as both will return a bool result. Of course the data type needs to be bool as well, but that is the same for either.

  • chekm8

    I'm also unable to reproduce this.  Sometimes I hate being crazy ;)

  • The Rhino

    I was unable to repro this in any form I tried.


  • EvanBlack

    Have you tried putting it into a precedence constraint

    P.S. I missed the rest of the expression off in the original post. I've added it now

  • ArBeeBee

    Maybe an IDW16 issue. On IDW15 (all I have to hand) it fails as I would expect-

    Attempt to parse the expression "@[User::FF" failed.  The token "@" at line number "0", character number "0" was not recognized. The expression cannot be parsed because it contains invalid elements at the location specified.

    This is an Int32 variable, being assigned to an Int32 property.



  • SSIS thinks an invalid expression is valid
Answer this question