Enterprise XML

tdb

I'm working with a project management system which can import and export MS Project XML files. I'm supposed to write a script that converts a custom spreadsheet into an XML file that can be imported to the system (somewhat of a WTF in itself; there's a REST API for the system as well, so I'm trying to advocate using that instead). To have something to work with (we don't have MS Project) I exported one project from the system to look at. A simple project with a single task got turned into almost 6000 lines of XML, most of which appears to be calendar definitions, duplicated for each job role and user assigned to the project. I also found this:

    <ExtendedAttribute>
      <FieldID>188744279</FieldID>
      <FieldName>Enterprise Cost1</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744280</FieldID>
      <FieldName>Enterprise Cost2</FieldName>
    </ExtendedAttribute>
    ...     
    <ExtendedAttribute>
      <FieldID>188744288</FieldID>
      <FieldName>Enterprise Cost10</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744289</FieldID>
      <FieldName>Enterprise Date1</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744290</FieldID>
      <FieldName>Enterprise Date2</FieldName>
    </ExtendedAttribute>
    ...     
    <ExtendedAttribute>
      <FieldID>188744318</FieldID>
      <FieldName>Enterprise Date30</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744319</FieldID>
      <FieldName>Enterprise Duration1</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744320</FieldID>
      <FieldName>Enterprise Duration2</FieldName>
    </ExtendedAttribute>
    ...     
    <ExtendedAttribute>
      <FieldID>188744328</FieldID>
      <FieldName>Enterprise Duration10</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744339</FieldID>
      <FieldName>Enterprise Flag1</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744340</FieldID>
      <FieldName>Enterprise Flag2</FieldName>
    </ExtendedAttribute>
    ...     
    <ExtendedAttribute>
      <FieldID>188744358</FieldID>
      <FieldName>Enterprise Flag20</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744379</FieldID>
      <FieldName>Enterprise Number1</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744380</FieldID>
      <FieldName>Enterprise Number2</FieldName>
    </ExtendedAttribute>
    ...     
    <ExtendedAttribute>
      <FieldID>188744418</FieldID>
      <FieldName>Enterprise Number40</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744479</FieldID>
      <FieldName>Enterprise Text1</FieldName>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <FieldID>188744480</FieldID>
      <FieldName>Enterprise Text2</FieldName>
    </ExtendedAttribute>
    ...     
    <ExtendedAttribute>
      <FieldID>188744518</FieldID>
      <FieldName>Enterprise Text40</FieldName>
    </ExtendedAttribute>

There's another set of similar attributes with different FieldIDs further down. At least we know where to look if we need some enterprise data.

@tdb said:

(we don't have MS Project)

what.

tdb

@beermouse said:

@tdb said:
(we don't have MS Project)

what.

Something about the license costing too much yadda yadda. I'm not a manager here, so it's not really my problem. I was able to convince management that using the REST API to stuff data into the service is a better idea, so thankfully I get to skip the XML creation phase.