Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
vintac
Partner - Contributor III
Partner - Contributor III

Problem with tSetDynamicSchema

Hello,

i'm using tSetDynamicSchema component with tSAPTableInput and i'm passing the shema to it via a tMap, but when i try to write the output i get the resulting table with columns replicated 4 times. This problem doesn't happen if i load the schema to tSetDynamicSchema from a delimited file instead. Below the job and the wrong results.

Is it a bug or am i doing something wrong?

vintac_1-1761645193452.png

vintac_0-1761645168284.png

 

Regards,

Vincenzo.

 

Labels (3)
1 Solution

Accepted Solutions
vintac
Partner - Contributor III
Partner - Contributor III
Author

ok, i think i found the problem, when i use the same tSetDynamicSchema first reading schema from a file and then reading from other component, for any reason the read schema from file option remains hiddenly selected even after the connection with the other component, and this is causing the erroneous behaviour: practically it's reading the schema from several sources at same time.

If you first deselect the read schema from file option and then connect with other source component, the results are correct. I think this is a kind of a bug that should be fixed anyway.

 

Regards,

Vincenzo.

View solution in original post

3 Replies
vintac
Partner - Contributor III
Partner - Contributor III
Author

ok, i think i found the problem, when i use the same tSetDynamicSchema first reading schema from a file and then reading from other component, for any reason the read schema from file option remains hiddenly selected even after the connection with the other component, and this is causing the erroneous behaviour: practically it's reading the schema from several sources at same time.

If you first deselect the read schema from file option and then connect with other source component, the results are correct. I think this is a kind of a bug that should be fixed anyway.

 

Regards,

Vincenzo.

Daniel_Castella
Support
Support

Test comment

Daniel_Castella
Support
Support

Second Test comment