Skip to main content
To homepage To homepage
Solved

REST: replace '' with NULL

N
Contributor
Forum|alt.badge.img+1
  • nmo
  • Contributor
  • 20 replies

I am trying to replace the CDATA Dynamics365 adapter with the TX REST connector (8.0.0) and I am having some issues where empty values from the API is interpreted as empty strings rather than NULL and as a result creates tables with incorrect datatypes

How do i set up a way to replace these empty strings with NULL values and keep the correct data types as well

I have tried with various combination of “Search and replace" on the endpoint as well as the individual nodes in the table builder without any luck.

I also have the “Empty fields as null” option enabled.

 

 

Best answer by Thomas Lind

Hi ​@nmo 

No those you already have should continue to work, but you will not be able to upgrade to a newer version of the provider if a bug or similar is found. So we would prefer that you do upgrade them to our own, but it is not an requirement for using the newest releases.

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

3 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1057 replies
  • April 24, 2025

Hi ​@nmo 

We have a feature for this.

It is present in version 8.0.0.0, but you should upgrade to the newest version to get all the benefits. A requirement to use 9.0.0.0 and newer is to be on the 6926.1 release or newer.

N
Contributor
Forum|alt.badge.img+1
  • nmo
  • Author
  • Contributor
  • 20 replies
  • April 24, 2025

I thought so, but  I was under the impression the CDATA connectors would stop working if I upgraded from my current version 6848.1

Is this not the case - I can upgrade to the newest release and still have my last CDATA datasource work?

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1057 replies
  • Answer
  • April 24, 2025

Hi ​@nmo 

No those you already have should continue to work, but you will not be able to upgrade to a newer version of the provider if a bug or similar is found. So we would prefer that you do upgrade them to our own, but it is not an requirement for using the newest releases.

Reply


Most helpful members this week

Terms and ConditionsCookie settings

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