Skip to main content
Solved

Nested API calls maxes out?


Hi,
As mentioned here https://support.timextender.com/data-sources-112/advanced-rsd-file-options-884?postid=7688#post7688 I'm having some issues with nested API calls using the CData REST provider. It looks like it maxes out at 1,000 calls per iteration. Is this the expected behaviour or is there a setting I haven't found?

Thanks!

Best answer by RLB

It turns out the settting Pagesize in REST provider 2023 was set to 1000. I've changed it to an arbitrary 99,999,999 and it works.

Apparently the 2020 provider has a similar pagesize parameter but it's not visible in the settings.

It's still weird because non-nested (but paginated) API calls with more than 1000 results work fine.

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

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

Hi @RLB 

Could you please create a new data source using the latest version of the Cdata REST 2023 provider and try to see if this resolves the issue?


  • Contributor
  • July 24, 2024
Christian Hauggaard wrote:

Hi @RLB 

Could you please create a new data source using the latest version of the Cdata REST 2023 provider and try to see if this resolves the issue?

Thanks, yes, I will try that. In fact I have tried a few weeks ago and failed.


  • Contributor
  • July 24, 2024

WIth the latest CData provider for REST 2023 I'm getting this error (some info redacted):

 

2024-07-24T12:40:11.970+02:00	1	[7|Q-Id]	[SQL |Messag] Query Failed: [SELECT	[some_fields]
	, 'datasource_name' AS [DW_SourceCode]
 FROM [REST].[table_name]]. Error: Could not load type 'RSSBus.RSBCancellation' from assembly 'RSSBus, Version=2.0.0.0, Culture=neutral, PublicKeyToken=123abc'.
2024-07-24T12:40:11.970+02:00	2	[7|Q-Id]	Could not load type 'RSSBus.RSBCancellation' from assembly 'RSSBus, Version=2.0.0.0, Culture=neutral, PublicKeyToken=123abc'.
RSSBus.RSBException
   at dwo230A.pNV..ctor(pGJ , RSBOperation , RSBItem )
   at dwo230A.pNV.t(pGJ , Object , RSBItem , pmx , aHH , Boolean )
   at dwo230A.pGJ.Iterate(RSBOperation , RSBItem )
   at dwo230A.UKE.c(RSBContext , pmE`1 , UKK , RSBItem , RSBCallback )
   at dwo230A.UKy.c(RSBContext )
   at dwo230A.UKy.Exec(RSBContext )
   at dwo230A.pNK.S(RSBOperation , pGJ )
   at dwo230A.pNK.e(RSBOperation , pNi )
   at dwo230A.pHV.ExecuteQuery(IDataStatement , QueryParameterCollection , Int32 )
   at dwo230A.aaG.ExecuteQuery(IDataStatement , QueryParameterCollection , Int32 )
   at dwo230A.Za.ExecuteQuery(IDataStatement , QueryParameterCollection , Int32 )
   at dwo230A.art.st()
   at dwo230A.arW.Wi()
   at dwo230A.mJ.ND(QueryParameterCollection )

It's why I kept trying with the 2020 provider which does mostly work.

 

More errors:

 

The CData provider seems to have a strangely long version number:

 

Also, after having added this CData prover, it keeps disappearing from the Manage CData Data Source Providers window. Probably related to this weird long version number.

Anyways I'm not able to test my nested API calls with the 2023 provider.


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

@RLB please upgrade TimeXtender to the latest version in order to solve the cdata version number issue, and subsequently test the 2023 provider


  • Contributor
  • July 28, 2024

Thanks, but that may take a while.
I can report however that the previous version of the CData provider (23.0.8770.0) does work with TimeXtender 20.10.50.64 but the issue remains. I did notice a (new) batch size setting in the REST provider that I did not see in version 20.0.7654.0. I played around with that setting with mixed results. Will investigate further at a later date.


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

@RLB please see the following post which may be relevant

 


  • Contributor
  • July 30, 2024

It turns out the settting Pagesize in REST provider 2023 was set to 1000. I've changed it to an arbitrary 99,999,999 and it works.

Apparently the 2020 provider has a similar pagesize parameter but it's not visible in the settings.

It's still weird because non-nested (but paginated) API calls with more than 1000 results work fine.


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

@RLB thanks for confirming. Please let me know if you would like me to raise a support ticket with Cdata, if so please send a log file or verbosity level 3 to support@timextender.com 


  • Contributor
  • July 30, 2024

Thanks @Christian Hauggaard but I don't think this warrants a support ticket with CData at this time.


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