Skip to main content
Solved

Join a ONE Data table with a Catalog Item in OneWeb

  • October 30, 2024
  • 4 replies
  • 45 views

  • Universe Traveller
  • 3 replies

I have a One Data table created by importing data from a .csv file.  I need to use some of the data in this table by joining it with an existing Catalog Item by creating a SQL Catalog Item so that I can implement some rules on it.  Where you select the source when starting to create the SQL Catalog Item I do not get an option to select oneData.  Is it even possible to do this in OneWeb?

Best answer by rafeeq.durowoju

Hey @Mel ,

Might I ask which version you are using?

I’ve just tried what you described by creating a VCI, adding a DQ rule to it, both at CI level, and at Monitoring Project (MP) level. 

I then made a change to the VCI by adding a new column, updated, and published all within ONE Desktop. When I return to the web application, I can see my new column and the DQ rule is still applied both at the CI level and at the MP level. I am able to run the DQ evaluation successfully on my VCI without any additional changes. All of this was tested in v15.2. 

 

Update:

Having tested the same in v14.5.0, I am seeing the behavior you described regarding the DQ mappings being removed when the VCI changes. 

Depending on your version/deployment type, I would recommend exploring your options regarding upgrading to version 15 where this issue seems to have been resolved. 


Regards, 

Rafeeq

 

View original
Did this topic help you find an answer to your question?

4 replies

Forum|alt.badge.img+3

Hey Mel, 

If you want to join two catalog items coming from differing sources, you would do this by using a VCI, within which you would use the Catalog Item Reader step to read the data from both CIs and join them together within your ONE Desktop plan. More information here.

Regards, 

Rafeeq


  • Author
  • Universe Traveller
  • 3 replies
  • November 4, 2024

Thanks @rafeeq.durowoju, that is what I am currently doing, and then pushing it to OneWeb where the rules are created and implemented on the combined data set in a Monitoring project.  But the problem I am facing with this is every time a change is made to the data set/VCI in OneDesktop and it is then pushed to OneWeb again all the rules that was previously implemented on it is removed.  It is not behaving the same way a SQL CI does, where you can amend the CI and it is just updated in the Monitoring project.  So hence my question if it is possible to create a SQL CI that joins with a OneData table.


Forum|alt.badge.img+3

Hey @Mel ,

Might I ask which version you are using?

I’ve just tried what you described by creating a VCI, adding a DQ rule to it, both at CI level, and at Monitoring Project (MP) level. 

I then made a change to the VCI by adding a new column, updated, and published all within ONE Desktop. When I return to the web application, I can see my new column and the DQ rule is still applied both at the CI level and at the MP level. I am able to run the DQ evaluation successfully on my VCI without any additional changes. All of this was tested in v15.2. 

 

Update:

Having tested the same in v14.5.0, I am seeing the behavior you described regarding the DQ mappings being removed when the VCI changes. 

Depending on your version/deployment type, I would recommend exploring your options regarding upgrading to version 15 where this issue seems to have been resolved. 


Regards, 

Rafeeq

 


  • Author
  • Universe Traveller
  • 3 replies
  • November 6, 2024

Hi @rafeeq.durowoju 

I appreciate that you are testing and trying to help so much.  I have 14.5.2 Desktop version but 14.5.0 Web version - so probably that is where my problem comes in.  I will request update to the Web version.  For now I have loaded the OneData data into a Snowflake table and things seem to be working fine.  I will try this again with version update.

Thank you again

Mel


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings