DSXchange

...I'll try to find time to give that scenario a spin also.

Ernie

hmmm. I tested a variety of changes, but in a different pattern....making changes in the source database after initial import and being sure they were imported correctly (the second time) and into both the ds table def and it's connected shared table definition....and then checking that notes, short...

Yes...the Connector import is more mature.....use it if you can. It not only avoids breaking things, it even brought the description updates added in Workbench into the "DataStage" tabledef for any DS developers who may not have access to Workbench. ...and yes, it creates the Datastage tab...

tag above should be <activitytime></activitytime> or <activitytime/> .

...and what happens when you map it directly to the output link (no stage variable and no derivation logic) ? For such a test you might want to reconsider your check boxes for null handling, and only check "replace NULLs with empty values".... You should get a lengthy set of </activityTime...

...just to make it clear from the entry above.... The Connector Wizard from inside DataStage (it is different than importing ODBC Table Definitions) is accessed from the same Import...Table Definitions.... menu, but it is the very top option..... select ODBC once you get into the wizard. It creates ...

There is no way to import tables within Workbench. They can be "viewed" there, but not imported.......Shared Tables can be imported: a) via bridges and brokers (using Import/Export Manager, or IDA) b) via Connectors (from inside of DataStage, FastTrack, IA) c) via .csv file manually using ...

This depends on the WSDL that you have.....for simple, scalar type, single row in, single row out web services (which is the type that WSTransformer supports without customization), the "input" to the web service is exactly what is defined as the individual parameters that make up the inpu...

it's hard to say exactly what your issue is, but at first glance it appears that perhaps there is something about the null/not null setting of the column, it's treatment in the transformer, and it's treatment in the xml stage, especially when everything comes out ok when you hard code it. What is yo...

Yes...I use this technique all the time, even in the release beyond 8.1......generally I use a Stage Variable (with Derivation of StageVar + 1) and then a Constraint on the StageVar (StageVar <= nnnnn ) where nnnnn is my desired number of generated rows.

Ernie

I had a chance earlier today to give it (importing tables and then updates to those same tables via the ODBC Connector and the Connector Wizard within DataStage) a try. Not only did it work perfectly, leaving all my Notes, Stewards, Term assignments, Short & Long Description edits in place, when...

Recently I have been living in the next release, and lineage thru Stage Variables there works great. I have specific examples that trace back directly....from an output link Derivation to a StageVariable used in that Derivation...then up above to the StageVariable Derivation and then upstream to the...

Hmm....I've tested this sequence of activity with other import methods (IDA as I recall recently) and it was fine, preserving descriptions, asset assignments, etc. That might be an anomaly with that particular broker. You might want to try the ODBC Connector import and see if that has better behavio...

Hi Doug. Indeed...creating Extension Mappings for each Transformer would @#&k. :) Seems to me there were some issues with Stage Variables at one point, but I recall them being corrected. I'll have to take a look. Aside from that, as I work more deeply with Workbench myself, and teach others, I'm...

You can't change the xpath...but you could code for it in advance.....each link could have its own xpath, and then do something else downstream, bring the links back together, etc. ...or, if the xml content is not "too" big, just change the xml itself in an upsteam transformer...easy if th...