Salesforce

XML Files Not Included in the Version Control Project (Magic xpa 3.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

XML Files Not Included in the Version Control Project (Magic xpa 3.x)

Objective

This Technical Note explains why the DataSourcesIndex.xml and ProgramHeaders.xml files are not included in the Version Control project container in the Version Control database.

Description

In Magic xpa, when we create a project, the information about the project is held in a number of source files. Each source file contains a Magic xpa object, such as a different repository and individual programs.

When we add a new Magic xpa project to Version Control, all source files related to the project information, such as DataSources.xml, menus.xml and rights.xml, are added to the Version Control database, while DataSourcesIndex.xml and ProgramHeaders.xml are excluded.

These two files are only relevant to each developer’s local copy. These two files maintain the information about data source indexes and the information regarding programs in the repository. They are used to improve performance and are built on the fly.

Example

Let's say you have a number of programs in the project under Version Control working with two different clients. You will have two different local copies of the project for these two clients with the same number of programs.

If one client adds a new program to the project in the Program repository and saves it by “checking in” the program, you can see that the newly added program’s information is also added to the local copy of the ProgramHeaders.xml.

Now, on the second client, this new information will not be in the local copy of Programsheaders.xml, since it is still the old version of the project.

So if you select “Get Latest version” of the project on the second client, a newly added program of the first client will get added to the local copy of the project and the information in ProgramHeaders.xml will be updated accordingly. Similarly, you will see the same behavior with DataSourcesIndex.xml, which is relevant to the local copy of each client.

Thus, you can see that both these files maintain the local information of the project and that they are not meant to be present in the Version Control database. Whenever you select “Get Latest version” of the project, they will be updated as per the project’s current status on the Version Control server.

Reference
Attachment 
Attachment