I have noticed in Postgres there will be a column that is varchar with a character limit and Replicate will replicate that data to my sql server environment with the same character limit, but then I will get an error saying that the data has been truncated. After doing some investigating in Postgres I was able to find that the data was able to exceed the character limit. As an example the character limit on the Postgres source is 200, but I have found columns (that include white space) that have 500 characters. Is there a work around for this so that the column on the target is able to expand dynamically or is this something that can be addressed in feature request? Has anyone else run into this issue?
Have you spoken to Qlik Support about this issue yet? If so, do you have a support case we can reference? If not, I think this is the best place to start.
I was advised from professional services to create an ideation ticket to see if this was an issue for anyone else in the QLIK Community before going through support. He may have an internal ticket for this issue that he created for us. To be fair, since upgrading to 7.X I have not noticed this issue, but it was a bigger problem during the implementation phase with my company. At the time we were on 6.5.
If you do encounter this issue on version 7.x I would recommend opening a ticket with Qlik Support and get their feedback. If we need to re-open this post we can.
