Skip to main content
Solved

Documentation for TimeXtender REST connector options/variables

  • April 19, 2024
  • 5 replies
  • 128 views

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7

In many of the tutorials for dealing with specific types of APIs reference is made to internal variables like {TX_CurrentPage} and others that can be leveraged to implement things like pagination. As far as I can find there does not seem to be a list of such items and what they do. Could this be made available?

 

Best answer by Thomas Lind

@rory.smith 

I added the part about builtin options Friday afternoon. There is not supposed to be more than these, but if new ones is added, I will make sure to add it to the guide and what their purpose is.

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

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

Hi @rory.smith 

The variables {TX_NextPage} and {TX_CurrentPage} are covered here under Pagination section

Please confirm if these are the variables you are referring to


rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • April 22, 2024

Hi @Christian Hauggaard ,

 

thanks - I think it would be more clear to have a separate section listing the variables and their specific meaning. While I can apply this tutorial, I would prefer to know exactly what these variables (and any future new ones) mean.


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

@rory.smith thanks for the feedback we will take this into account going forward


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • April 22, 2024

@rory.smith 

I added the part about builtin options Friday afternoon. There is not supposed to be more than these, but if new ones is added, I will make sure to add it to the guide and what their purpose is.


andrew.gebhard
TimeXtender Xpert
Forum|alt.badge.img+2

Hi @Thomas Lind, would it be possible to document the data-type names and conversions for the REST data source? 

For example, I am trying to override datatypes on a data source in ODX to make all string type fields nvarchar(max). Using datatype contains(ignore case) = ‘string’ does not work.

Would be great to know what the datatypes are called, and what they translate to in data-lake and SQL. 

I realize that override datatypes only takes effect if you delete the data files from the storage blob. string to varchar(max) works as expected. 

 

Kind regards,

Andrew


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