Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I have Vizlib Writeback table in the app.
I was asked to remove one column and to add another column (which is from real field ).
I have also wizard and also script, I tried to remove the column and add another one both in script and wizard and it throws me errors when i try to update the rows.
Please assist.
Thanks
Inna
Hello Inna, which error is showing?
Could you please share a screenshot of it, or copy and paste the error description?
Hu,
yes please:
Hi,
This message is not actually an error, but rather a warning from the Vizlib Writeback extension.
When a new column is created in the Qlik writeback table, the extension checks whether the corresponding field also exists in the destination table configured in the Vizlib Server (PostgreSQL database). In this case, your newly created field does not exist in the destination table, which is why the warning "Fields in destination do not match" is displayed.
The writeback process can only save data for fields that exist both in the Qlik configuration and in the destination database table. Therefore, any values entered in the new column will not be persisted unless a matching column exists in PostgreSQL.
There are two possible solutions:
Recommended approach: Contact the Vizlib Server administration team and request that the new column be added to the destination PostgreSQL table (under the Destination configuration, see attached screenshot). Once the column exists in the database, you can add it to the Qlik writeback table and data will be saved correctly.
Alternative approach: If modifying the PostgreSQL table is not feasible, keep using the existing column (instead of dropping it) and only change the label displayed to users in Qlik by enabling Custom Display Label (screenshot also attached). This changes the column name shown in the frontend without affecting the underlying database mapping.
In summary, the warning is expected behavior and indicates that the new Qlik field is not currently mapped to a corresponding field in the writeback destination table.