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.
In Data Migrator, I have a need to move data from a staging table into a finalized table, transforming it as I go. After the transformation, if the record passes muster, I want to delete the record from the staging table. If it doesn't pass muster, I want to leave it in the staging table where it will be addressed via user intervention. I have devised a two flow process where I make the insertion in flow 1, and then in flow 2 join the staging and finalized tables, deleting where matches exist. This seems straightforward.
But some complication comes into play in the event the same record gets submitted twice in the same run. This is a possible situation as the end user can update records multiple times between runs. In this event, the keying on the duplicates is the same.
Is there a part of the tool that allows me to delete the record in the source and insert the record in the target in the same flow? This would allow me to delete or save the record as appropriate.
SQL Server 2005 for both tables, Data Migrator 7.6.1.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
I have chosen to tackle this problem with a SQL Server "Unique Identifier" field type that will give each record in the staging table a unique key to search on. The mapping algorithm will carry this field to the result table and I will use it in the deletion process in the second flow.
Thanks anyway!
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007