I'm hoping that too. Not only that we would have to modify quite a lot of workbenches, but there are things that I would not know how to do in another way, like the following:
- Create Dynamic Attributenames according to some deduction logic in a custom transformer... - Make Joins with the ArcSDEQuerier: WHERE Foreignkey = &OBJECTID ... and so on ... how should this be done when we cannot use the ampersand or the @Value() - Function inside of transformers anymore? Greetings, Jeff On 5/3/07, Bégin, Daniel <[EMAIL PROTECTED]> wrote:
Gasp! I'm getting really nervous reading these lines. We have entire production processes (Hundreds of workbenches) that use &attributename, @value(attributename) or $(macrovalue). Does it mean we are going to have to modify all our workbenches to keep moving with new releases ??? Please, tell me we wont! Daniel Bégin Canada center for topographic information - Sherbrooke ------------------------------ *From:* [email protected] [mailto:[EMAIL PROTECTED] *On Behalf Of *Jason Birch *Sent:* 2 mai 2007 19:08 *To:* [email protected] *Subject:* RE: [fme] Variables and AttributeCreator Jeff wrote: > I'd like to stress that this kind of working, with &attributename and @Value(Attributename) > inside of Transformers is very important for us and we'd not like it to disappear! I had some lengthy discussions with Safe staff just before and during the UC. The long and the short of it is that they appear to be fixed on doing away with these "hacks" in order to insulate users from unexpected results when placing these special characters (&, @, etc) within transformers without knowing what they do. They did commit to ensuring that alternative means of accessing these items would be developed as required, so if you're missing something make sure to let them know asap. Jason
-- Jeff Konnen INSER SA Switzerland +41 (0) 21 643 77 11
