DSXchange

I usually like to use the field() function in a transformer for this...but it may depend on how big your strings are. Take the first field where <SeqNum> is your delimeter (everything to its left) and the second field when </SeqNum> is the delimiter (everything to its right) and concatenate them tog...

Ditto to the easier install comment above. I've installed 8.5 on various machine configurations about 15 times and each of them has been a far more smooth and enjoyable experience than times in the past with earlier releases. Average is about three hours for me so far....and without holding my breat...

Could be many things. Some things to look at: First...are you certain that your xml message is getting out of the xml stage looking the way it should? Send it thru a transformer and also to a Sequential File with delimeter and quote character equal to NONE. Are you sending out a pure xml chunk? Avoi...

I don't use it often because I don't have a license for BO...so it's only when I've been at customer sites......and I'd have to venture a guess, but I'll bet that 90% (maybe even much higher) of all use of the bridge is for "import," not export. The desire is generally to include BO in lin...

I don't know if there were any problems with "this" in particular. There certainly has been a LOT added in terms of capabilities and patches to other things, with 8.1 FP1 and then the 8.1.2 addition for Foundation Tools which includes Business Glossary and Metadata Workbench. However, ther...

I've seen odd things like this when the values of the innermost child are duplicated. First, to confirm it, you might try adding a dummy column and element in the contact method (at the same level as ID), and give it something unique, such as @INROWNUM from an upstream transformer. Make the XPATH (d...

What is your goal?

I once wrote a job that was an infinite loop (destructive read from queueA and then write a new message to queueA), but it had no purpose except to easily have a job that would run for an enormous amount of time without worrying about things like queue depth.

Ernie

Just send the single big column to a Sequential Stage with Format that has delimeter of NONE and quote character of NONE.

Add an output link.
Put a single column on it, like "xmlContent"
Make it longvarchar and give it a long length, like 99999
Send it to a transformer where you can use your favorite method for changing all <dummy> and </dummy> to blanks.

Ernie

Most of the time the error is due to inability to parse rdbms-specific SQL in a user defined SQL statement. The parser handles ANSI standard SQL and where possible, ignores certain dialect specific things in order to determine lineage. ....I've never seen the error cause a problem with lineage, howe...

You may need to put an artificial "containing" element around mid/measure/eligible/performance. Take a look at the Description property for each column on the input link.....you should see something like: .../.../mid/text() .../.../measure/text() . . Change these so that they same somethin...

Use the xml method. Do exactly as Ray suggests. Put in some related terms manually. Dump out an xml export. Look at it. Match it and it will work. The xml import is by far the best method...it supports related terms, stewards, assigned assets, custom attribute creation and addition, etc. Ernie

We're all dating ourselves here. Aren't too many of us around who can still "read" hex, let alone do calculations on it or immediately recognize a zone decimal from a packed decimal from an integer... (and so on)... Sigh. A lost art.

Ernie

Not sure what harish_ means then ....I might have misunderstood...I thought that a trigger column was created, and in fact, is working, but now is appearing in the xml. But I might have mis-read it.

Ernie

Check the Description property of that column in the input link. Make sure it doesn't have any "/--anything" in it. The slash dictates that the stage should apply xpath to that column.

Ernie