Skip to main content
Solved

Data not visible


  • Contributor
  • 5 replies

Good Day All, 

At this moment we have the following challenge: Client is utilizing TX version 20.10.43.64. Client requested us to add new fields. We've modified the *.rsd file, columns are being created however data is not visible after we've deplooy and execute. We've verified the source and can confirm that data is entered. 

Is there something that we've missed or overlooked? 

Appreciate your support in here. 

Regards, 

Marc

Best answer by Marc

Hi Christian, 

We are currently receiving support from Thomas on this manner. Seems more challenging then originally anticipated. 

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

6 replies

bas.hopstaken
TimeXtender Xpert
Forum|alt.badge.img+4
  • TimeXtender Xpert
  • 86 replies
  • June 17, 2024

Hi @Marc ,

Did you run the synchronize task after changing the RSD files? This ensures the new columns are detected.

After running the synchronize task, you need to synchronize the ODX Server (right-click ODX Server → Synchronize Objects). Once it is synced, the new columns should be visible in the data warehouse layer as well.


  • Author
  • Contributor
  • 5 replies
  • June 17, 2024

Hi @bas.hopstaken, synchronize task have been executed. Columns are visible however data fields are empty and missing data.

Thanks. 


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • 1035 replies
  • June 18, 2024

Fields that appear empty while existing in the RSD file can be due to two things.

  1. The XPath in the field descriptor points incorrectly to the field making it appear empty
  2. The JSONPath setup does not point to the right level hence it can’t find the data.

This <api:set attr="JSONPath" value="$." /> is the default JSONPath for most RSD files, but it can be that it is on a lower level that the data exists. You can change the Data Model setup before generating the file to see how it affects this. If it is set to FlattenedDocuments it can aggregate more than one setup in this field using a ; to separate each setup.


rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • 662 replies
  • June 18, 2024

Hi,

 

additionally if the table you are loading into is incremental or a history table, it won't populate new fields unless new records are loaded in. You may get more information if you set the verbosity on the logging to level 3 and verify that the raw data is being loaded from source.


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi @Marc have you had a chance to try the suggestions above?


  • Author
  • Contributor
  • 5 replies
  • Answer
  • June 26, 2024

Hi Christian, 

We are currently receiving support from Thomas on this manner. Seems more challenging then originally anticipated. 


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