Skip to main content
Solved

invalid column name


Forum|alt.badge.img
  • Contributor
  • 26 replies

Hello everyone,

After the odx transfer task for API, when I click on the preview, I get the “invalid column name” error. This warning also occurs while executing in the data warehouse and stops execute.  What should I do? I wanted to use aliases but I have 575 columns.

I tried to re-deploy the table with differential deployment disabled. 

 

Version: 6143.1

 

My column name example is below: it is very long

properties_parameter_WS10M_RANGE_202109

 

Thanks

Best Regards

Best answer by ebay

it was a JSON file and it merged into a single column by changing the schema. Finally, I got a column by subject, not by dates. (Exp instead of ‘WS10M_RANGE_202109’  I got WS10M_RANGE)

Best Regards

 

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

5 replies

Forum|alt.badge.img
  • Author
  • Contributor
  • 26 replies
  • March 16, 2023

--solved-- how?

I deleted the '_' in the path separator and it worked. But column names didn’t change. Why? Can someone explain to me?


Forum|alt.badge.img+3
  • Contributor
  • 82 replies
  • March 16, 2023

Which provider are you using ?  For root cause, can you configure logging for the provider data source in the portal (example image below) and generate two log files?  One for the non-working scenario (original column name) and then for the working scenario (updated column name)

 

 


Forum|alt.badge.img
  • Author
  • Contributor
  • 26 replies
  • March 17, 2023

Provider type:

Managed ADO.NET

Provider version:

22.0.8257.0

Provider name:

JSON


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

Please see the following documentation regarding the path separator property for the JSON provider https://cdn.cdata.com/help/DJH/ado/RSBJSON_p_PathSeparator.htm

It appears that the path separator controls the table name based on the file name. I am not sure how changing this property would resolve an “invalid column name” error. Also, the default value for the path separator is ‘_’, so deleting '_' in the path separator property should in theory not have made a difference, since the default would be used which is the same. Perhaps you synchronized the data source after changing the path separator, which actually solved the “invalid column name” error (rather than changing the path separator property).

 


Forum|alt.badge.img
  • Author
  • Contributor
  • 26 replies
  • Answer
  • March 31, 2023

it was a JSON file and it merged into a single column by changing the schema. Finally, I got a column by subject, not by dates. (Exp instead of ‘WS10M_RANGE_202109’  I got WS10M_RANGE)

Best Regards

 


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