# Komment setup

### Data Connection Settings

In Qlik SaaS editions you don’t have to specify your data connection when setting up Komment. You just keep it as is:

![Data connection](/files/yZgmv3tiQ7sLIolqDekj)

This is the only change you need to do in the UI inside your Qlik Sense app when you have configured what your writeback objects should contain. You can now move to the last setup step which is to add the needed logic to the Data load script.

### Load script‍

While still in the UI of Komment, go to the **Setup** section and press the **Preview Load Script** button. Press **Initialize Data Model** to have your load script updated with a new section in the data load editor.

&#x20;As you have not chosen a specific QVD Data Connection you need to modify the script slightly but as you can see here it is very easy to do. Just replace "**undefined**" or **"undefined/"** with the name of your desired Data Storage. In the below example "**undefined**" is replaced with "**DataFiles**".

![Change in load script](/files/-Ma3AMKal6O8-r8PAh6h)

&#x20;As the SaaS edition works a bit different from Enterprise edition, you must use “**/**” after **DataFiles** instead of "**\\**".

![](/files/-Ma3BUAasb0imefambBN)

### QVD access

The QVDs that are saved when users save data using Komment can be accessed either via the hub or directly in the data load editor:

![Hub - Data](/files/-Ma3CqHdyjXTZeFyFEMG)

![Data load editor - Data connections](/files/-Ma3D3QjqGXq_F0GNYAE)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.extendbi.com/komment/qlik-saas-1/komment-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
