Skip to main content
Solved

Cleanse component pur_value and out_value

  • February 2, 2024
  • 5 replies
  • 81 views

Forum|alt.badge.img+1

I have a ā€˜provider_name’ cleansing component under ā€˜provider’ component. When I test the ā€˜provider_name’ cleansing component on DQS in a test plan, the values on pur* and out* fields look good. And the provider component shows the propertied of the name component as

Ā 

but for some reason, none of my changes are reflected or seen when the component is deployed with changes and subject is reprocessed. Am I missing something? I did debug at the name level and the component level, the values come out right but not after being deployed and reprocessed. Any suggestions?

Best answer by Ales

Hi @sgilla , I’m afraid this is a specific to TIBCO IBI/OMNI and not really to the Ataccama core engine.

Please reach out to Tibco support.

Thanks,

Ales

5 replies

Ales
Ataccamer
Forum|alt.badge.img+2
  • Ataccamer
  • February 2, 2024

Hi @sgilla, it’s not clear from your message what exactly you deploy to the server - if it’s just a single component or all the related plans. Sometimes it happens that the mapping is not correctly applied in the server wrapper plan/component when you deploy just the inner component.Ā  Would you please be able to share the full context - wrapper plan and components in here?

This context would help to identify the issue.

Thanks,

Ales


Forum|alt.badge.img+1
  • Author
  • Data Pioneer
  • February 2, 2024

Hello Ales,

Deploying the whole bundle with the small change on a name cleansing component, which was not reflecting after the subject reprocess. The wrapper plan etc are intact no changes there.Ā 

Solution I figured isĀ to onramp the records as deleted and let omni mark them ā€˜INACTIVE’ on the source and instance tabled. ThenĀ re-inserting them as a new ā€˜INS’ record to the ramp. Thats theĀ way the cleansing rules are seen applied.

So I am confused as to why a subject re-process did not help and neither did the record re-load (ā€˜UPD’), instead only the solution above where I inactivate all records and re-activate is working. Is there a better solution than this where we do not go through these multiple steps of InactivationĀ and then activation?

Ā 

Thank you for the quick response.


Forum|alt.badge.img+1
  • Author
  • Data Pioneer
  • February 2, 2024

Let me add this is for Tibco ibi omni OHD application.


Ales
Ataccamer
Forum|alt.badge.img+2
  • Ataccamer
  • Answer
  • February 5, 2024

Hi @sgilla , I’m afraid this is a specific to TIBCO IBI/OMNI and not really to the Ataccama core engine.

Please reach out to Tibco support.

Thanks,

Ales


Forum|alt.badge.img+1
  • Author
  • Data Pioneer
  • February 5, 2024

thank you @AlesĀ