As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I am coding a pretty big chunk of fields from one table to another, and I need to manage the null entries very carefully. I have devised transforms that do this, but they seem to function differently depending on where they come in the list. Some only work if they're one of the first fields in the flow. Can anybody explain why this is?
This is causing me more than a bit of trouble, as I am having to manage ordering carefully to keep all of them running correctly.
None of these fields seem to have any commonality, so if anyone can tell me what to look for so that I can get my ordering correct I would greatly appreciate it.
J.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
I'm sorry you found this confusing; Test Transforms just simulates the load. (For you FOCUS programmers it does so with TABLE while the load is usually a MODIFY). If you see this inconsistenty just with columns for which you ommitted a transformation, you can avoid it by explicitly setting those columns to the value MISSING. In older releases that may turn the columns red, but as long as the column is in fact nullable it should work.
N/A
Posts: 397 | Location: New York City | Registered: May 03, 2007