Create Schedule Activities from File V2

Support for SOAP is deprecated starting with Unifier 23.10.

Description

This option will allow user to process a P6 XML file and add activities and resources to an existing Unifier schedule sheet. Along with activity information this process will also take activity spread information. Since the activity spread information data can be a lot, this method allows user to send in information in a .zip file.

Support

Installation: ASP and Self host

Level Yes or No
Company Level No
Project/Shell Level Yes

Prototype

public XMLObject createScheduleActivitiesFromFileV2(String shortname, String authcode, String projectNumber, String sheetname, String scheduleoptions, String iszipfile, FileObject[] files);

Parameters

Parameter Description
Shortname identifier of the company, company's short name
Authcode authentication key for the company, in text string
projectNumber Identifier of the project/shell.
sheetName Identifies the name of the schedule sheet.
iszipfile This tag identifies if the file provided under files tag is a zip file or .xml file with just activity and resource information. If user wants to send activity spread information, the value of this tag should be yes and the file provided under files tag should be a zip file containing activity/ resource information and the spread information.
files FileObject containing the Activity / Resource information and the activity spread information. FileObject is made up of two components String filename (this should be the name of the zip file) and the zip file with two files, one for activity / resource information and one with activity spread information. Name of the activity/ resource information should be same as the one given under <scheduleoptions>.<ActivityFileName>tag and the name of the name of the activity spread information should be same as the one given under <scheduleoptions>.<SpreadFileName>.
scheduleOptions

This element will allow message to carry optional information. Following are the tags under this element:

<MapName/>

<ActivityIdentifier/>

<CBS_NoOfLevelsToMerge/>

<CBS_StartMergeFrom/>

<ActivityFileName/>

<SpreadFileName/>
MapName Name of the data mapping that should be used while processing XML file
ActivityIdentifier Possible values are GUID, ID. ID is the tag of Activity Id in Primavera.
CBS_NoOfLevelsToMerge

This parameter will take a numeric value. This parameter can be used by user to specify how many levels (CBS Levels) in P6 XML file should be merged.

EXAMPLE: Assume that P6 has following structure: (5.ON.DA.DA03.F350.U11.095.ABC20.CAct04). If you specify 3 then three levels will be merged, and the 3 segments will be based on the next parameter (CBS_startmergefrom)
CBS_StartMergeFrom
  • This parameter will take a numeric value. Value of this parameter will be used to determine the level from which this merge should start.
  • EXAMPLE: In the above example, if a user specifies 2, the system will start from level 2 and merge ON, DA and DA03. So after the merge the CBS Code build by import program will be 5.ONDADA03.F350.U11.095.ABC20.CAct04
ActivityFileName Name of the file that contains the activity and resource information. Please refer to files tag
SpreadFileName Name of the activity spread file name. Please refer to files tag

Return Value

See Appendix B: Return Values.

Sample Method

createScheduleActivitiesFromFileV2("acme","acme_authcode","Proj-0001","Schedule Sheet 001", "<XMLContent>","yes","<scheduleoptions>",files);

Additional Information

Format of spread file should be similar to Sample Spread Data example.

While processing spread information, the system will only look for <amt> tag.

If the Import from external source option is checked in Unifier and spread information is not available in XML file then system will error out. This error condition is also valid when this tag is not available in the XML file.

Activity File should start and end with <List_Wrapper> tag

Spread file should not contain any <List_Wrapper> tag