Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    3
  • Subscribers subscribers
    12
  • Views views
    181
  • Users 0 members are here
Related
Options

PPM: Assistance with Bulk Project Import Using "Import Request from XML"

Pedro_X

I am attempting to perform a bulk import of projects into OpenText PPM using the "Import Request from XML" option, but I am encountering the following error: "Missing expected element".

I would appreciate guidance on:

  1. The mandatory elements that the XML file must contain for a successful import.
  2. An example of a valid XML file or a template that I can use to properly structure the projects for import.
  3. Any other available options or methods in OpenText PPM to efficiently perform a bulk project import.
  4. I have attached the XML file I am currently using for this process for your review.

Thank you for your assistance in determining the best way to proceed with the bulk import of projects.

regards

Fullscreen creaproyecto_ppm_en.xml Download 
<?xml version="1.0" encoding="UTF-8"?>
<requests date_format="YYYY-MM-DD">
  <request>
    <request_type>SGP: Proyecto general</request_type>
    <field>
      <token>REQ.P.KNTA_PROJECT_NAME</token>
      <value>Prueba Import</value>
    </field>
    <field>
      <token>REQ.P.KNTA_PROJECT_MANAGER</token>
      <value>Admin User</value>
    </field>
    <field>
      <token>REQ.P.KNTA_PLAN_START_DATE</token>
      <value>2024-01-01</value>
    </field>
    <field>
      <token>REQ.P.KNTA_PLAN_FINISH_DATE</token>
      <value>2024-03-31</value>
    </field>
    <field>
      <token>REQ.P.SGP_CODIGO</token>
      <value>PR_09_2022_PI_1234</value>
    </field>
	<field>
      <token>REQ.P.REGION</token>
      <value>CHILE</value>
    </field>
  </request>
</requests>

  • 0  

    Hi Pedro,

    Whatever you're trying to do, I don't think that "Import Request from XML" is the right tool to batch create projects. This will only create requests, and if you want to batch-create requests (including Proposals), you're much better using the "Data Import/Export" feature even if it's still officially under development. More info on how to enable it on this thread. This lets you download an Excel template for a request type with all the columns for the fields of the request type, and you can then fill the Excel file with requests info and upload it to PPM in order to create all the requests. 

    But what you're looking for is to create Projects, and for this I'm only aware of the PPM XML Importer, which is a different tool which is supposedly only to be used as part of a PSO engagement. You should be able to find it to download in some threads of this forum if you're looking for it, but use it at your own risk (works great though when it works!).

  • 0 in reply to   

    Thank you, Etienne,

    With the shared content, I was able to download and use the 'PPM_XML_Importer_9.3'. I successfully imported a project with typical fields; however, I have fields that are of the 'Autocomplete List' type and are dependent on other fields, and I am unable to import them. Could you guide me on how to populate these values?

    Currently, I receive the following error:

    Import Identifier: 1729117957207
    Import Started: 16 de octubre de 2024 19:32:37 CLST
    Test Mode - no records will be created in ITG.
    Abort process after 10 failures.
     
    Project identified by "Testing of XML Project1"
    Error 2: Fail to apply value 'Territorial' for field REQ.SGP_TIPO. If it is validation error, check the validation definition to make sure all TOKENs it depends on can be resolved. Detail error: Uno de los tokens de la validación no se pudo analizar. Esto puede deberse a que un nombre de token no es válido o a que faltan datos en el campo que representa el token. (KNTA-10073).
    Error 2: Error validating field REQ.SGP_SUBINSTRUMENTO: contains multiple values, but field does not support multiple values.
    Error 2: Fail to apply value 'Individual' for field REQ.SGP_SUB_TIPO. If it is validation error, check the validation definition to make sure all TOKENs it depends on can be resolved. Detail error: Uno de los tokens de la validación no se pudo analizar. Esto puede deberse a que un nombre de token no es válido o a que faltan datos en el campo que representa el token. (KNTA-10073).
    Error 2: Fail to apply value 'Implementación' for field REQ.SGP_FASE_INST. If it is validation error, check the validation definition to make sure all TOKENs it depends on can be resolved. Detail error: Uno de los tokens de la validación no se pudo analizar. Esto puede deberse a que un nombre de token no es válido o a que faltan datos en el campo que representa el token. (KNTA-10073).


    Import Finished: 16 de octubre de 2024 19:32:37 CLST
    Import Completed with Errors.
    The result is:
        # passed: 0.
        # failed: 1.
        # skipped: 0.
    Excel:
    *Field Prompt: Project Name: (OK) Project Type (OK) Project Managers: (OK) Planned Start: (OK) Planned End: (OK) Region (OK) Short Desc (OK) Status (OK) Creation Date (OK) Código: (OK) Instrumento: (OK) Fase instrumento: (error) Autocomplete List Subinstrumento: (error) Autocomplete List Tipo: (error) Autocomplete List Subtipo: (error) Autocomplete List
    Identifier Project Name Project Type Project Managers Planned Start Planned End Region REQ.DESCRIPTION REQ.STATUS_ID REQ.CREATION_DATE REQ.SGP_CODIGO REQ.SGP_INST REQ.SGP_FASE_INST REQ.SGP_SUBINSTRUMENTO REQ.SGP_TIPO REQ.SGP_SUB_TIPO
    1 Testing of XML Project1 Proyecto General Admin User 01-01-2024 01-12-2025 CHILE Description Testing of XML Project1 Adjudicación 01-01-2024 PR_01_0001_PI_0001 ENCCRV Implementación FERI Territorial Individual

    Regards

  • 0   in reply to 

    Sorry, this is a tool to be used by Professional Services, and I'm not that familair with it.

    I assume that one workaround would be to temporary change your project field validations to simple ACLs that do not depend on other fields, and revert back to the original validations after projects batch loading is completed.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.