Qlik Automation Export 64 encoded file to Gitlab and importing again as back-up

[CB_JKUO]

Hi All,

I am trying to export Qlik Apps into Gitlab, which I want to use for back-up purposes.

So using Qlik Automation, I export an App to Base 64 encoded File and create this file in Gitlab.

This is the content of the file:

However, when I want to import this file again into Qlik SaaS, it seems the file content has changed completely:

I have used different methods for this import:

- The Gitlab block: Get File From Repository

- The Gitlab Block : Raw API Request

Both give me different different file content when importing the file.

Has anyone else encountered a similar problem?

[SameulChukwezi]

---

@CB_JKUOCompassTree wrote:

Hi All,

I am trying to export Qlik Apps into Gitlab, which I want to use for back-up purposes.

So using Qlik Automation, I export an App to Base 64 encoded File and create this file in Gitlab.

This is the content of the file:

However, when I want to import this file again into Qlik SaaS, it seems the file content has changed completely:

I have used different methods for this import:

- The Gitlab block: Get File From Repository

- The Gitlab Block : Raw API Request

Both give me different different file content when importing the file.

Has anyone else encountered a similar problem?

---

It sounds like you're encountering issues with file integrity when exporting and importing between Qlik and GitLab. Different methods for file retrieval from GitLab might handle encoding or file format differently. Ensure that the Base64 encoding and decoding processes are correctly implemented and consistent across both export and import. It might also help to verify the file content by decoding it manually before re-importing. Double-check the GitLab API settings and the Qlik Automation configurations to ensure compatibility. If the problem persists, reaching out to Qlik or GitLab support could provide additional insights.