21.01.2013 Views

QlikView Reference Manual.pdf - QlikCommunity - QlikView

QlikView Reference Manual.pdf - QlikCommunity - QlikView

QlikView Reference Manual.pdf - QlikCommunity - QlikView

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

l TX.xml<br />

l LA.xml<br />

l SL.xml<br />

l SO.xml<br />

l BM.xml<br />

l CT.xml<br />

l RP.xml<br />

The files DocProperties.xml, AllProperties.xml, DocInternals.xml and TopLayout.xml<br />

all contain property settings for the different parts of the document. DocBinary.dat contains user sensitive<br />

data, such as passwords.<br />

9.2 Source Control<br />

It is possible to connect <strong>QlikView</strong> Desktop to a source control system; the Microsoft Source Control Plug-in<br />

API (MSSCCI) is the provider used for this function. There are many MSSCCI provider DLLs that enable<br />

integration with different source control systems and are available for downloading. The <strong>QlikView</strong> implementation<br />

is based on the 1.2 version of the MSSCCI API.<br />

Once connected to a source control system, <strong>QlikView</strong> developers can add projects to source control. During<br />

the Add process the:<br />

l <strong>QlikView</strong> document is saved<br />

l Project folder is created<br />

l Project files are exported into the project folder<br />

l Project files are added to source control<br />

l Project settings file is created<br />

The project settings file is stored in the local project folder. The file is named [<strong>QlikView</strong>DocumentName]prj.scc<br />

and contains the settings necessary to access the source control information for the project. The<br />

project settings file is not included in the files managed by the source control system. The existence of the<br />

project settings file tells <strong>QlikView</strong> that a given document is managed by a source control system. In addition,<br />

<strong>QlikView</strong> has to be able to find and load the needed MSSCCI Provider DLL, in order to treat the document<br />

as attached to source control. This check is performed every time a document is opened in <strong>QlikView</strong>.<br />

If the document is attached to source control, the status bar will contain an indication of the document’s<br />

status.<br />

<strong>QlikView</strong> integration with source control only affects document layout. No actual data loaded into Qlik-<br />

View is placed into nor fetched from, source control. The operation, Get Project from Source Control will<br />

load a document that contains everything except data. A Reload must be executed to populate the document<br />

with data.<br />

After a <strong>QlikView</strong> document is connected to source control saving the document will automatically check<br />

out the files that have changes. <strong>QlikView</strong> does not provide any other way of checking out the project files.<br />

If Source Control system is not available while performing document Save, then <strong>QlikView</strong> will try to work<br />

"offline", i.e. remove read only flags from the modified files and save the latest version. On the next document<br />

save, when Source Control system is available, <strong>QlikView</strong> will perform check out for all locally modified<br />

files.<br />

On document save, project files are not checked in. To check in document updates to source control, the<br />

Check In Pending Changes menu item must be used. A single <strong>QlikView</strong> check in operation can generate<br />

several change sets. As a result, rollback between randomly selected change sets does not guarantee that the<br />

document will be in a stable state.<br />

52

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!