File System Task Expressions

  • Raunak Jhawar (10/4/2010)


    Also, have you implemented any checkpoints in your package...

    No. I don't use checkpoints as they never worked for what we really needed them for.

    I appreciate the link, Raunak, but it has nothing to do with the issue at hand. There were no deleted variables. The issue is that Expressions in the File System Task just don't work as one might expect. As, I add, they work in other Tasks.

    I confirmed this issue with Brian Knight, BTW. He says that Expressions in the File System Task don't work the way I wanted them to work and that you do indeed have to have additional variables to make the File System Task function. And no, he doesn't know why either.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Brandie Tarvin (10/5/2010)


    ... I confirmed this issue with Brian Knight, BTW. He says that Expressions in the File System Task don't work the way I wanted them to work and that you do indeed have to have additional variables to make the File System Task function. And no, he doesn't know why either.

    Brandie, thanks for the Brian Knight reference. I always use variables with the FileSystem Tasks so I not seeing the problems you did.

    (Now, I need to make a record of this.)



    Alvin Ramard
    Memphis PASS Chapter[/url]

    All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

    For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • Brandie Tarvin (10/5/2010)


    Stefan Krzywicki (10/4/2010)


    Then I put a File System Task on the page and clicked it to select it. I created a variable with the scope of File System Task called Conc

    I made it a string like the other 3 and then went to the properties panel for that variable. I changed EvaluateAsExpression to True and then built the expression there! Right under the property EvaluateAsExpression there's a field called Expressions and you can set the expression there instead of in the File System Task.

    I went back into the File System Task, set it up as a Rename File

    IsSourcePathVariable True

    SourceVariable User::Source

    IsDestinationPathVariable::True

    DestinationVariable User::Conc

    I ran it, it worked like a charm.

    I hope this works for you!

    Yeah, but that's not the way I wanted to use the File System task. I was trying to avoid the creation of unnecessary variables and just re-use the ones I'd already had. It didn't work.

    As far as where to report bugs, it's somewhere on Tech Net. I believe if you google for it, you can find the link.

    Rats. Sorry! I thought I'd found it. I'd left work right after posting yesterday and on the way home got to thinking more about it. When creating the expression in File System Task, it asks you what property to relate it to. I'd been picking Destination, but there's nowhere to then reference that propertly later. There isn't even an option to pick a System variable for destination the way there is for source. I'd been hoping that was the answer, but alas it is not.

    I'm not really sure why they'd have that setup in File System Task if they're not going to let you use it.

    --------------------------------------
    When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
    --------------------------------------
    It’s unpleasantly like being drunk.
    What’s so unpleasant about being drunk?
    You ask a glass of water. -- Douglas Adams

  • The issue here might fall under the classification of undocumented feature, if you know what I mean.



    Alvin Ramard
    Memphis PASS Chapter[/url]

    All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

    For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • Alvin Ramard (10/5/2010)


    The issue here might fall under the classification of undocumented feature, if you know what I mean.

    HA!

    Now if I could just use DBCC Timewarp to fix it ahead of when it was broken?

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Brandie Tarvin - Tuesday, October 5, 2010 4:47 AM

    Stefan Krzywicki (10/4/2010)


    Then I put a File System Task on the page and clicked it to select it. I created a variable with the scope of File System Task called ConcI made it a string like the other 3 and then went to the properties panel for that variable. I changed EvaluateAsExpression to True and then built the expression there! Right under the property EvaluateAsExpression there's a field called Expressions and you can set the expression there instead of in the File System Task.I went back into the File System Task, set it up as a Rename FileIsSourcePathVariable TrueSourceVariable User::SourceIsDestinationPathVariable::TrueDestinationVariable User::ConcI ran it, it worked like a charm. I hope this works for you!

    Yeah, but that's not the way I wanted to use the File System task. I was trying to avoid the creation of unnecessary variables and just re-use the ones I'd already had. It didn't work.As far as where to report bugs, it's somewhere on Tech Net. I believe if you google for it, you can find the link.

  • Brandie Tarvin - Tuesday, October 5, 2010 4:47 AM

    Stefan Krzywicki (10/4/2010)


    Then I put a File System Task on the page and clicked it to select it. I created a variable with the scope of File System Task called ConcI made it a string like the other 3 and then went to the properties panel for that variable. I changed EvaluateAsExpression to True and then built the expression there! Right under the property EvaluateAsExpression there's a field called Expressions and you can set the expression there instead of in the File System Task.I went back into the File System Task, set it up as a Rename FileIsSourcePathVariable TrueSourceVariable User::SourceIsDestinationPathVariable::TrueDestinationVariable User::ConcI ran it, it worked like a charm. I hope this works for you!

    Yeah, but that's not the way I wanted to use the File System task. I was trying to avoid the creation of unnecessary variables and just re-use the ones I'd already had. It didn't work.As far as where to report bugs, it's somewhere on Tech Net. I believe if you google for it, you can find the link.

    This is 8 years later, but thank you Brandie and all those on this thread. You all saved me a world of pain and frustration in getting this to work with individual files I'm iterating through. And it kills me to have to create unnecessary extra variables in order to do so, but so be it. THANKS!

Viewing 7 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic. Login to reply